Triple
T27192500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Step I |
E683511
|
entity |
| Predicate | usesDichotomy |
P55152
|
FINISHED |
| Object | Extraversion–Introversion |
—
|
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: Extraversion–Introversion | Statement: [Step I, usesDichotomy, Extraversion–Introversion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDichotomy Context triple: [Step I, usesDichotomy, Extraversion–Introversion]
-
A.
usesDecisionBoundaryType
chosen
Indicates that one entity applies or relies on a specific type of decision boundary in making classifications or decisions.
-
B.
usesDivisor
Indicates that one entity employs another entity as a divisor in a division or modular arithmetic operation.
-
C.
decisionSplit
Indicates that a single decision point branches into multiple alternative outcomes or paths.
-
D.
bothUse
Indicates that two entities make use of, employ, or utilize the same resource, method, or object.
-
E.
usesDH
Indicates that one entity employs or relies on another entity as a designated hitter (DH) in a baseball-related context.
- 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_69eefad140408190b8586fdebcf9af46 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 9:32 a.m.