Triple
T1566806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disney XD |
E33449
|
entity |
| Predicate | hasInternationalVersions |
P7228
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Disney XD, hasInternationalVersions, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInternationalVersions Context triple: [Disney XD, hasInternationalVersions, true]
-
A.
hasInternationalVersion
chosen
Indicates that an entity has a corresponding version or counterpart adapted for use in multiple countries or international contexts.
-
B.
hasInternationalStatus
Indicates that an entity holds a recognized status, role, or standing at the international level rather than being limited to a single country or local jurisdiction.
-
C.
isInternational
Indicates that something has a connection to, involves, or extends across more than one country.
-
D.
internationalAvailability
Indicates that something is available or accessible across multiple countries or regions beyond a single national boundary.
-
E.
hasInternationalService
Indicates that an entity provides or is connected to transportation or communication services that operate across national borders.
- 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_69a885f11b048190935025a035302715 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90fccd4b48190a44012888a00af7f |
completed | March 5, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69a907b872f0819096b3df6ad502c63e |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:27 p.m.