Triple
T11264225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aralsk |
E266641
|
entity |
| Predicate | wasPortUntil |
P57849
|
FINISHED |
| Object | late 20th century |
—
|
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: late 20th century | Statement: [Aralsk, wasPortUntil, late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasPortUntil Context triple: [Aralsk, wasPortUntil, late 20th century]
-
A.
wasIn
Indicates that an entity existed, occurred, or was located within a particular place or context during a specified time or situation.
-
B.
servedAsMainSeaportUntil
chosen
Indicates that an entity functioned as the primary seaport for another entity up to a specified point in time.
-
C.
wasA
Indicates that an entity previously had a certain role, type, or classification in the past.
-
D.
wasLast
Indicates that one entity occurred or appeared after all others in a sequence, making it the final item or event.
-
E.
port
Indicates a relationship where one entity serves as a harbor, access point, or interface through which another entity can enter, exit, or connect.
- 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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e94d56048190bf808e1bc2188714 |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d7879bc56c8190b2e8d2193f29de05 |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:31 p.m.