Triple
T3636579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IV |
E77082
|
entity |
| Predicate | usesSubtractiveNotation |
P49733
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [IV, usesSubtractiveNotation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSubtractiveNotation Context triple: [IV, usesSubtractiveNotation, true]
-
A.
isSubtractiveCombination
Indicates that one entity is formed or derived by subtracting one or more components, values, or parts of another entity.
-
B.
distinguishingNotation
Indicates that one entity uses a specific notation or symbol to distinguish or differentiate another entity from similar ones.
-
C.
typicalNotation
Indicates that one entity is the standard or commonly used symbolic representation (notation) for another entity.
-
D.
notationSystem
Indicates a relationship where one entity is the system or method of notation used to represent or encode another entity.
-
E.
usesRomanNumerals
Indicates that something represents numbers or sequences using the Roman numeral system rather than standard Arabic digits.
- 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_69ad85dd0be48190b738990cb20c4731 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3278bb8819098bbeac023410111 |
completed | March 8, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69adb842be7c8190b7dfdb7c906f294c |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb902e61c81908f10494f828e260f |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:24 p.m.