Triple
T530220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyropoeon Valley |
E12205
|
entity |
| Predicate | currentState |
P127
|
FINISHED |
| Object | largely filled in and obscured |
—
|
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: largely filled in and obscured | Statement: [Tyropoeon Valley, currentState, largely filled in and obscured]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentState Context triple: [Tyropoeon Valley, currentState, largely filled in and obscured]
-
A.
stateRock
Indicates that an entity is in a solid, rock-like physical state or condition.
-
B.
typeOfState
Indicates that one state is a specific kind or category of another, more general state.
-
C.
status
chosen
Indicates the current condition, state, or standing of an entity within a given context.
-
D.
positionInState
Indicates that one entity occupies or holds a specific position, role, or status within a particular state or condition of another entity.
-
E.
continuityStatus
Indicates the state of whether something continues without interruption or has been broken, paused, or reset over time.
- 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4985e51908190a34aa82ea9dbee1e |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b257108190a537dffbb9d621b5 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.