Triple
T3772652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euphrátēs |
E83232
|
entity |
| Predicate | knownAsOneOf |
P50838
|
FINISHED |
| Object | longest rivers of Western Asia |
—
|
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: longest rivers of Western Asia | Statement: [Euphrátēs, knownAsOneOf, longest rivers of Western Asia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownAsOneOf Context triple: [Euphrátēs, knownAsOneOf, longest rivers of Western Asia]
-
A.
recognizedAs
Indicates that one entity is acknowledged or accepted as having the identity, role, status, or classification of another entity.
-
B.
alsoKnownAs
Indicates that one entity is an alternative name, alias, or designation for another entity.
-
C.
namedIn
Indicates that one entity is explicitly mentioned or referenced by name within another entity (such as a document, statement, or record).
-
D.
alsoServesAs
Indicates that one entity has an additional role, function, or identity that it fulfills simultaneously with its primary one.
-
E.
knownForCollectionOf
Indicates that one entity is recognized or notable specifically for its collection or assemblage of another type of entity.
- 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_69ad8b235e608190b5a2b1d1bfcef50b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc3219b881908a2f82126f9a679d |
completed | March 8, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69adc050cc5c81909d9855f866f3c26d |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc0fe3e3c8190bd886c7745c172a0 |
completed | March 8, 2026, 6:33 p.m. |
Created at: March 8, 2026, 3:36 p.m.