Triple
T32486249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Survivor |
E830248
|
entity |
| Predicate | hasAdaptationInCountry |
P21186
|
FINISHED |
| Object | United States |
—
|
NE NERFINISHED |
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 States | Statement: [Survivor, hasAdaptationInCountry, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdaptationInCountry Context triple: [Survivor, hasAdaptationInCountry, United States]
-
A.
hasAdaptationsIn
Indicates that something possesses or exhibits adaptations within a particular context, environment, or domain.
-
B.
adaptationCountry
chosen
Indicates the country in which an adaptation (such as a remake, translation, or localized version) of an original work is produced or set.
-
C.
availableInCountry
Indicates that something can be legally or practically obtained, accessed, or used within a specified country.
-
D.
displayedInCountry
Indicates that something is shown, exhibited, or made visible within the boundaries of a specified country.
-
E.
isPlayedInRegion
Indicates that an instance of something (such as a game, media, or event) is available to be played or occurs within a specified geographic region.
- 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_69f34920aa4081908d8fb0277414b911 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: May 1, 2026, 12:58 a.m.