Triple
T11230736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N1 |
E265811
|
entity |
| Predicate | numberComponent |
P91585
|
FINISHED |
| Object | "1" indicating primary or first‑order route |
—
|
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: "1" indicating primary or first‑order route | Statement: [N1, numberComponent, "1" indicating primary or first‑order route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberComponent Context triple: [N1, numberComponent, "1" indicating primary or first‑order route]
-
A.
number
Indicates that one entity is associated with a specific numerical value or count in relation to another entity or context.
-
B.
numericPartRepresents
chosen
Indicates that a numeric component of something stands for or encodes a specific value, property, or aspect of that thing.
-
C.
containsNumber
Indicates that one entity includes or has at least one numeric value or digit within it.
-
D.
symbolNumber
Indicates a relationship where a specific numerical identifier is assigned to or associated with a particular symbol.
-
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_69d6aac656d48190b275efaa7d6074ee |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9026e1c81909456ac946bbba972 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d75cfdf7a88190aae21572e57ef208 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.