Triple
T8268590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expedition Robinson |
E193361
|
entity |
| Predicate | formatCoreElement |
P23479
|
FINISHED |
| Object | tribe divisions |
—
|
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: tribe divisions | Statement: [Expedition Robinson, formatCoreElement, tribe divisions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formatCoreElement Context triple: [Expedition Robinson, formatCoreElement, tribe divisions]
-
A.
hasFormatElement
chosen
Indicates that one entity includes, is composed of, or is associated with a specific structural or formatting component of its overall format.
-
B.
formatPartOf
Indicates that one entity functions as a component or segment within the overall structure or composition of another entity.
-
C.
formatMayChange
Indicates that the format or structure of something is subject to modification and may not remain consistent over time.
-
D.
formatCategory
Indicates how an item is classified or grouped according to its format or presentation type.
-
E.
formatBefore
Indicates that one item’s format or formatting must occur or be applied prior to another item’s format or formatting.
- 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_69ca82e081d48190986beaa51f498ab9 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb795127ac81908196008f5579f83f |
completed | March 31, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69cb70a4525481909399d313a6247ace |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:50 p.m.