Triple
T32613958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USCSS |
E833733
|
entity |
| Predicate | usedByFictionalEntity |
P189734
|
FINISHED |
| Object | United Americas |
E1884023
|
NE 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: United Americas | Statement: [USCSS, usedByFictionalEntity, United Americas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByFictionalEntity Context triple: [USCSS, usedByFictionalEntity, United Americas]
-
A.
usedInFictionalWork
Indicates that something (such as a concept, object, or character) appears or is employed within a specific fictional work.
-
B.
ownedByFictionalCharacter
Indicates that something is possessed or owned by a fictional (not real-world) character.
-
C.
attendedByFictionalCharacter
Indicates that a fictional character is present at, participates in, or is an attendee of a particular event or gathering.
-
D.
fictionalEntityIn
Indicates that a fictional entity appears in, is set within, or is part of the context of another work, setting, or universe.
-
E.
discoveredByFictionalCharacter
Indicates that something (such as an object, place, or concept) is discovered by a fictional character within a narrative.
- F. None of above. chosen
Provenance (5 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fbca6c066c8190a1599202f341417f |
completed | May 6, 2026, 11:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34861c59c48190a14851268ddbd7ba |
completed | June 18, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fbc9d0854c8190aa00093274afebb8 |
completed | May 6, 2026, 11:08 p.m. |
Created at: May 1, 2026, 1:06 a.m.