Triple
T37209144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Creek |
E922251
|
entity |
| Predicate | sharesCaptivityWith |
P202773
|
FINISHED |
| Object | Spirit |
—
|
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: Spirit | Statement: [Little Creek, sharesCaptivityWith, Spirit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesCaptivityWith Context triple: [Little Creek, sharesCaptivityWith, Spirit]
-
A.
sharesFateWith
Indicates that two or more entities are bound to experience the same outcome, destiny, or consequences.
-
B.
sharesWith
Indicates that one entity gives another entity access to or use of something it possesses.
-
C.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
D.
sharesSlainWith
Indicates that two or more entities have killed the same target or share responsibility for the same slaying event.
-
E.
sharesBunkerWith
Indicates that one entity occupies or uses the same bunker as another entity.
- 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_69f76ea4849481909b4a3073efb0114c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00b6e163308190adeb1d6eb8558641 |
completed | May 10, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_6a00b67e0e388190b08ad66cee4cb0d7 |
completed | May 10, 2026, 4:46 p.m. |
| PDg | Predicate description generation | batch_6a00b6e0b954819094e63589d718b9af |
completed | May 10, 2026, 4:48 p.m. |
Created at: May 3, 2026, 4:15 p.m.