Triple
T26603868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sons of the Desert |
E667713
|
entity |
| Predicate | hasOrganizationInPlot |
P177511
|
FINISHED |
| Object | Sons of the Desert lodge |
—
|
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: Sons of the Desert lodge | Statement: [Sons of the Desert, hasOrganizationInPlot, Sons of the Desert lodge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrganizationInPlot Context triple: [Sons of the Desert, hasOrganizationInPlot, Sons of the Desert lodge]
-
A.
hasOrganizationFor
Indicates that one entity possesses, is associated with, or is responsible for a particular organization in relation to some context or purpose.
-
B.
hasAgencyInPlot
Indicates that an entity actively influences or drives events within the narrative’s plot.
-
C.
isKeyToPlotOf
Indicates that something plays a crucial, defining role in driving or enabling the main events or structure of a plot.
-
D.
hasOrganBy
Indicates that one entity possesses or includes another entity as an organ or component part.
-
E.
hasResidentOrganization
Indicates that an organization is based in, operates from, or maintains a primary presence within a particular place or facility.
- 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_69ee9cfd20348190bb1255d2603efb7a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: April 27, 2026, 2:13 a.m.