Triple
T194776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Julian Edelman |
E3794
|
entity |
| Predicate | weightInKilograms |
P1575
|
FINISHED |
| Object | approximately 90 |
—
|
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: approximately 90 | Statement: [Julian Edelman, weightInKilograms, approximately 90]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weightInKilograms Context triple: [Julian Edelman, weightInKilograms, approximately 90]
-
A.
weight
chosen
Indicates a relationship where a numerical value quantifies how heavy an entity is, often used to measure or compare mass or load.
-
B.
averageWeight
Indicates the typical or mean weight value associated with an entity or group of entities.
-
C.
usesMeasurementSystem
Indicates that one entity adopts or applies a particular system of measurement defined by another entity.
-
D.
bodySize
Indicates the relative physical magnitude or scale of an entity’s body, such as how large or small it is.
-
E.
usesMetric
Indicates that one entity adopts, applies, or relies on a particular metric or measurement standard in its operation, evaluation, or description.
- 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_69a2548debd48190ae3a06d6e65b53c6 |
completed | Feb. 28, 2026, 2:35 a.m. |
| NER | Named-entity recognition | batch_69a25969425081908e178db8ba4631c2 |
completed | Feb. 28, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69a25677da14819094cd02868fd30c83 |
completed | Feb. 28, 2026, 2:44 a.m. |
Created at: Feb. 28, 2026, 2:41 a.m.