Triple
T8108707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burbn |
E189289
|
entity |
| Predicate | reasonForPivot |
P6009
|
FINISHED |
| Object | overly complex feature set |
—
|
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: overly complex feature set | Statement: [Burbn, reasonForPivot, overly complex feature set]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForPivot Context triple: [Burbn, reasonForPivot, overly complex feature set]
-
A.
reasonForSplit
Indicates the cause, motivation, or circumstance that led to a separation or breakup between entities.
-
B.
selectionReason
Indicates the reason or justification for choosing or selecting one entity over alternatives.
-
C.
reasonForAlignment
Indicates the justification or cause that explains why one entity’s alignment, stance, or position corresponds to or matches another.
-
D.
reasonForChange
chosen
Indicates that one entity serves as the cause, justification, or motivation for a modification or change in another entity or state.
-
E.
statedReason
Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
- 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_69ca82b9d5848190a24672775d5c5011 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb42fa40e08190955fccec1a28eb34 |
completed | March 31, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69cb04a2ed1c8190b73562321ad688bc |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:32 p.m.