Triple
T17691249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Moscow |
E441031
|
entity |
| Predicate | stateBuildingProcess |
P128593
|
FINISHED |
| Object | territorial expansion |
—
|
LITERAL FINISHED |
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: territorial expansion | Statement: [House of Moscow, stateBuildingProcess, territorial expansion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateBuildingProcess Context triple: [House of Moscow, stateBuildingProcess, territorial expansion]
-
A.
processBuilding
Indicates the action of performing operations or transformations on a building or building-related data.
-
B.
hasBuildingStatus
Indicates the current condition, classification, or operational state assigned to a building.
-
C.
rulingStateAtConstruction
Indicates the political state or authority that held ruling control over a place or structure at the time it was originally constructed.
-
D.
builderStatus
Indicates the current state or condition of a builder in relation to its construction or configuration process.
-
E.
constructionPhase
Indicates the specific stage or period an entity is in within an overall construction or building process.
- F. None of above. chosen
Provenance (4 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47152306c819086d483d87348db5d |
completed | April 19, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 10:03 a.m.