Triple
T18564497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PUA-B |
E453727
|
entity |
| Predicate | numericType |
P132524
|
FINISHED |
| Object | None |
—
|
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: None | Statement: [PUA-B, numericType, None]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numericType Context triple: [PUA-B, numericType, None]
-
A.
numericTypeFocus
Indicates that the relationship or context specifically concerns the numeric type or numerical aspect of the associated entities or values.
-
B.
doubleType
Indicates that one entity is of a double-precision numeric type or that a value is being treated or converted as a double-precision floating-point number in relation to another entity.
-
C.
numericalProperty
Indicates that an entity is associated with a specific numeric value or measurable quantity.
-
D.
numericPartRepresents
Indicates that a numeric component of something stands for or encodes a specific value, property, or aspect of that thing.
-
E.
floatType
Indicates that an entity has a specific floating-point data type or is categorized as a floating-point numeric value.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53afd8114819093b57d86f8213311 |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:42 a.m.