Triple
T28673238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christmasland |
E725784
|
entity |
| Predicate | truePurpose |
P79
|
FINISHED |
| Object | prison for kidnapped children |
—
|
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: prison for kidnapped children | Statement: [Christmasland, truePurpose, prison for kidnapped children]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: truePurpose Context triple: [Christmasland, truePurpose, prison for kidnapped children]
-
A.
traditionalPurpose
Indicates that something serves a role, function, or use that is established by long-standing custom or tradition.
-
B.
findsPurposeThrough
Indicates that one entity derives its sense of purpose, meaning, or fulfillment through its relationship with or actions involving another entity.
-
C.
purpose
chosen
Indicates that one entity exists, is done, or is used in order to achieve, support, or serve the goal, function, or intended outcome of another entity.
-
D.
cultPurpose
Indicates that an entity (such as a cult, group, or organization) exists or operates with a specific overarching purpose, goal, or objective.
-
E.
tagPurpose
Indicates the intended role, function, or use associated with a given tag in a particular context.
- 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6563263948190937ca191a52c0700 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 5:05 a.m.