Triple
T14651684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanyoxarces |
E344001
|
entity |
| Predicate | disputedIdentity |
P86192
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Tanyoxarces, disputedIdentity, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disputedIdentity Context triple: [Tanyoxarces, disputedIdentity, Yes]
-
A.
hasDisputedIdentityWith
Indicates that two entities are associated with conflicting, uncertain, or contested identifications, such that their true or correct identities are in dispute relative to each other.
-
B.
disputedIdentities
chosen
Indicates that there is disagreement or conflict over how the identities of the involved entities are defined, classified, or recognized.
-
C.
identityIssue
Indicates that an entity is experiencing uncertainty, conflict, or problems related to its sense of identity or self-definition.
-
D.
disputed
Indicates that there is active disagreement or contestation over the validity, ownership, interpretation, or status of the relationship or claim between the entities.
-
E.
disputeKnownAs
Indicates that a particular dispute is also referred to by an alternative name or title.
- 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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb517e7648190b9fc73d6cdbb68de |
completed | April 14, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:27 a.m.