Triple
T25796166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle Park Plate |
E649688
|
entity |
| Predicate | traditionalDistance |
P17802
|
FINISHED |
| Object | six furlongs |
—
|
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: six furlongs | Statement: [Middle Park Plate, traditionalDistance, six furlongs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalDistance Context triple: [Middle Park Plate, traditionalDistance, six furlongs]
-
A.
distanceMetric
Indicates a quantitative measure of how far apart two entities are within a given space or according to a specified metric.
-
B.
formerDistance
Indicates that a distance or spatial separation between entities existed in the past but no longer holds in the present.
-
C.
distanceCharacteristic
chosen
Indicates a relationship where an entity is described or constrained by some property or measure of distance (e.g., range, spacing, or separation).
-
D.
cityBlock
Indicates that one entity is a city block that contains, is the location of, or is otherwise spatially associated with the other entity.
-
E.
primaryDistance
Indicates the main or most significant measure of distance between two entities in the relationship.
- 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_69e7ab34f8c8819099f6c4dabdabf129 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 22, 2026, 6:30 a.m.