Triple
T1991774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Tower of the World Trade Center |
E43265
|
entity |
| Predicate | complexNumber |
P8195
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [South Tower of the World Trade Center, complexNumber, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: complexNumber Context triple: [South Tower of the World Trade Center, complexNumber, 2]
-
A.
symbolInComplexAnalysis
Indicates that a given symbol is used specifically within the context or notation of complex analysis.
-
B.
number
chosen
Indicates that one entity is associated with a specific numerical value or count in relation to another entity or context.
-
C.
hasComplex
Indicates that one entity possesses, is associated with, or is part of a larger composite structure or complex formed with another entity.
-
D.
oppositeNumber
Indicates that one number is the additive inverse of the other, such that their sum equals zero.
-
E.
vector
Indicates that one entity is a vector associated with, representing, or characterizing another entity (such as a quantity with magnitude and direction, or a carrier/representative of something).
- 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_69a88714cf2c819081644be450b8356e |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8ee02dc81908fec9fd8df7a4f40 |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb79ad6888190be99943a9c73cf3e |
completed | March 7, 2026, 5:28 a.m. |
Created at: March 4, 2026, 7:37 p.m.