Triple
T35536537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moldavia |
E1026944
|
entity |
| Predicate | tributaryStatusStartTime |
P183396
|
FINISHED |
| Object | 15th 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: 15th century | Statement: [Moldavia, tributaryStatusStartTime, 15th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tributaryStatusStartTime Context triple: [Moldavia, tributaryStatusStartTime, 15th century]
-
A.
reclamationStartDate
Indicates the date on which a reclamation process or activity is initiated.
-
B.
hasHeadwaterStatus
Indicates that a water body holds the status of being a headwater or source segment within a hydrological system.
-
C.
tributary
Indicates that one watercourse flows into and feeds another, contributing its water to a larger stream, river, or lake.
-
D.
subordinationDate
Indicates the date on which one entity formally became subordinate to another in a hierarchical relationship.
-
E.
hasTributaryRelationWith
Indicates that one entity maintains a tributary relationship with another, typically involving the payment of tribute or acknowledgment of subordinate status.
- 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f7340e4819092a1a47f7028e63f |
completed | May 3, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79ec14ce08190b22cee0b40d33743 |
completed | May 3, 2026, 7:15 p.m. |
Created at: May 3, 2026, 4:04 p.m.