Triple
T27279314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vicente Luque |
E688285
|
entity |
| Predicate | reachApprox |
P14301
|
FINISHED |
| Object | 75.5 in |
—
|
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: 75.5 in | Statement: [Vicente Luque, reachApprox, 75.5 in]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reachApprox Context triple: [Vicente Luque, reachApprox, 75.5 in]
-
A.
reaches
Indicates that one entity extends or moves until it makes contact with, attains, or arrives at another entity or point.
-
B.
intendedReach
Indicates the target audience, scope, or extent that something is meant or designed to affect or be accessible to.
-
C.
maximumReach
chosen
Indicates the greatest extent, distance, or limit that something can reach or influence within a given context.
-
D.
canReach
Indicates that one entity is able to access, arrive at, or establish a path to another entity.
-
E.
availabilityTarget
Indicates that something is the intended object, resource, or condition whose availability is being specified, monitored, or constrained.
- 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_69ef3558cf8881909595ef89daf6e14a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6272c4eb081909b224d630b7c48d6 |
completed | May 2, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 11:05 a.m.