Triple
T34248859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benjamin Rand |
E878676
|
entity |
| Predicate | providesToChance |
P152241
|
FINISHED |
| Object | shelter |
—
|
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: shelter | Statement: [Benjamin Rand, providesToChance, shelter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesToChance Context triple: [Benjamin Rand, providesToChance, shelter]
-
A.
chanceElement
Indicates that the relationship or outcome involves randomness or probabilistic chance rather than being deterministic.
-
B.
wouldProvide
Indicates that one entity is willing or expected to supply or furnish something to another entity under certain conditions.
-
C.
conversionChanceOnNormal
Indicates the probability that a conversion will occur under normal or standard conditions.
-
D.
promotionPossibility
Indicates the potential or eligibility for an entity to be advanced to a higher rank, position, or status.
-
E.
sometimesProvides
chosen
Indicates that one entity occasionally or intermittently provides something (such as a service, resource, or support) to another entity, but not on a consistent or guaranteed basis.
- 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_69f349b3618481909df955b063f305b2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe38be079c8190a240191ac0e73e3a |
completed | May 8, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69fe350344508190930de2218156ca02 |
completed | May 8, 2026, 7:09 p.m. |
Created at: May 1, 2026, 1:56 a.m.