Triple
T5558491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vitasta |
E145706
|
entity |
| Predicate | isIdentifiedWith |
P6594
|
FINISHED |
| Object | Hydaspes of Greek sources |
—
|
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: Hydaspes of Greek sources | Statement: [Vitasta, isIdentifiedWith, Hydaspes of Greek sources]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIdentifiedWith Context triple: [Vitasta, isIdentifiedWith, Hydaspes of Greek sources]
-
A.
hasIdentity
chosen
Indicates that one entity is the same as, or is identified as, another specific entity or identifier.
-
B.
hasIdentityDocument
Indicates that an entity possesses or is associated with a specific identity document.
-
C.
hasSocialIdentity
Indicates that an entity possesses or is associated with a particular social identity, such as a role, group membership, or socially recognized status.
-
D.
identityStatus
Indicates the current state or condition of an entity’s identity, such as whether it is verified, active, pending, or otherwise classified.
-
E.
identifierTypeManaged
Indicates that one entity is responsible for administering or controlling the type or scheme of identifiers used for another entity.
- 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_69c008fcaf788190bafa02a1917ee73b |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0201529a88190bf0135e032b048ea |
completed | March 22, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69c01b10bbf8819098655839c03b7832 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.