Triple
T26522752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian White movement in exile |
E670000
|
entity |
| Predicate | formedCommunityIn |
P26923
|
FINISHED |
| Object | France |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: France | Statement: [Russian White movement in exile, formedCommunityIn, France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedCommunityIn Context triple: [Russian White movement in exile, formedCommunityIn, France]
-
A.
formsCommunityIn
chosen
Indicates that an entity comes together with others to establish or participate in a community within a particular context or location.
-
B.
formsBiStateCommunityWith
Indicates that two entities jointly constitute or participate in a shared bi-state community spanning both of their jurisdictions.
-
C.
communityType
Indicates the classification or category of community to which an entity belongs (e.g., urban, rural, online, professional).
-
D.
collaboratingCommunity
Indicates that two or more entities are actively working together toward shared goals or projects as part of a community relationship.
-
E.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69eeb31b6dcc8190b30632dc3928a0c0 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 27, 2026, 1:29 a.m.