Triple
T27617359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bill has adventures independently |
E700473
|
entity |
| Predicate | occursWithout |
P165088
|
FINISHED |
| Object | support network |
—
|
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: support network | Statement: [Bill has adventures independently, occursWithout, support network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occursWithout Context triple: [Bill has adventures independently, occursWithout, support network]
-
A.
occursFor
Indicates that an event, process, or condition takes place in relation to, or on behalf of, a particular entity or context.
-
B.
occursTo
Indicates that an event, idea, or realization happens in or comes to the mind or awareness of an entity.
-
C.
occursWhen
Indicates that one event or condition happens at the same time or is triggered under the circumstances defined by another event or condition.
-
D.
occursVia
Indicates that an event, process, or state happens or is realized through a specified method, mechanism, medium, or intermediary.
-
E.
neverSeenWithout
Indicates that one entity is always accompanied by another and is not observed in situations where the other is absent.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 27, 2026, 2:13 p.m.