Triple
T28690256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Survivor: One World |
E729256
|
entity |
| Predicate | sharesCamp |
P194655
|
FINISHED |
| Object | both tribes lived on the same beach |
—
|
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: both tribes lived on the same beach | Statement: [Survivor: One World, sharesCamp, both tribes lived on the same beach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesCamp Context triple: [Survivor: One World, sharesCamp, both tribes lived on the same beach]
-
A.
sharesCampusWith
Indicates that two entities are located on or use the same campus or campus facilities.
-
B.
sharesPlatformWith
Indicates that two entities operate on, are available through, or participate within the same platform or system.
-
C.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
D.
shareWith
Indicates that something is given, disclosed, or made accessible by one entity to another entity.
-
E.
sharesFeatureWith
Indicates that two entities have at least one common attribute, property, or characteristic in common.
- F. None of above. chosen
Provenance (4 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
| PDg | Predicate description generation | batch_69fd7fd9be2881908a7f00e0e8822de8 |
completed | May 8, 2026, 6:16 a.m. |
Created at: April 28, 2026, 5:35 a.m.