Triple
T34860175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Simson |
E1004844
|
entity |
| Predicate | sharesProvisionsWith |
P124918
|
FINISHED |
| Object | the outcasts from Poker Flat |
—
|
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: the outcasts from Poker Flat | Statement: [Tom Simson, sharesProvisionsWith, the outcasts from Poker Flat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesProvisionsWith Context triple: [Tom Simson, sharesProvisionsWith, the outcasts from Poker Flat]
-
A.
sharesRitesWith
Indicates that two entities participate in or observe the same religious, ceremonial, or ritual practices.
-
B.
sharesOwnershipWith
Indicates that two or more entities jointly hold ownership rights or stakes in the same asset, resource, or organization.
-
C.
sharesWith
chosen
Indicates that one entity gives another entity access to or use of something it possesses.
-
D.
sharesRulesWith
Indicates that two entities follow, are governed by, or operate under the same set of rules or regulations.
-
E.
sharesRuleWith
Indicates that two or more entities are governed by, comply with, or are associated with the same rule or set of rules.
- 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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0042524d8c8190884a10fce669ae95 |
completed | May 10, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_6a0041e89bd881909e32764699bcb89b |
completed | May 10, 2026, 8:29 a.m. |
Created at: May 3, 2026, 4 p.m.