Triple
T3524433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ES |
E74503
|
entity |
| Predicate | quoteConvention |
P6184
|
FINISHED |
| Object | index points |
—
|
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: index points | Statement: [ES, quoteConvention, index points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: quoteConvention Context triple: [ES, quoteConvention, index points]
-
A.
quoteProvision
Indicates that one entity supplies or presents a quotation or price estimate to another entity.
-
B.
logicConvention
Indicates a relationship where entities participate in or are associated with a convention, event, or standard related to logic or logical systems.
-
C.
quoteDescription
Indicates that one entity provides a textual description or explanation of a quoted statement or quotation associated with another entity.
-
D.
abbreviationStyle
Indicates the specific way in which something is abbreviated, such as the format, punctuation, or capitalization used in its shortened form.
-
E.
notation
chosen
Indicates a conventional way of symbolically representing or writing something, such as concepts, quantities, or operations, within a specific system.
- 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_69ad85d0c5488190a3d8e02ebd01a1aa |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc68b15881909b407486946ec3c5 |
completed | March 8, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69adae121a048190b03825a001d21f49 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.