Triple
T20143710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ID |
E491241
|
entity |
| Predicate | numericEquivalent |
P39995
|
FINISHED |
| Object | 360 |
—
|
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: 360 | Statement: [ID, numericEquivalent, 360]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numericEquivalent Context triple: [ID, numericEquivalent, 360]
-
A.
numericPartRepresents
Indicates that a numeric component of something stands for or encodes a specific value, property, or aspect of that thing.
-
B.
numeralValueOfX
chosen
Indicates that a given numeral corresponds to, or represents, the numeric value of, the entity X.
-
C.
numberDescribedAs
Indicates that a number is characterized, labeled, or referred to using a particular description or phrase.
-
D.
numericValueInIsopsephy
Indicates that a given entity has a specific numerical value when calculated according to the rules of isopsephy (the Greek letter-to-number system).
-
E.
numericCode
Indicates that an entity is associated with a specific numerical identifier or classification code.
- 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6679cbc388190bb2b444a69a597a6 |
completed | April 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:33 p.m.