Triple
T10624603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H3RC |
E250289
|
entity |
| Predicate | associatedWithLengthOverall |
P18065
|
FINISHED |
| Object | 399.94 m |
—
|
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: 399.94 m | Statement: [H3RC, associatedWithLengthOverall, 399.94 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithLengthOverall Context triple: [H3RC, associatedWithLengthOverall, 399.94 m]
-
A.
associatedWithBodyStyles
Indicates a relationship where something (such as a product, model, or item) is linked or connected to one or more specific body styles.
-
B.
typicalLength
chosen
Indicates the usual or characteristic length associated with an entity or phenomenon.
-
C.
properLengthMeasuredIn
Indicates that the proper (intrinsic or rest-frame) length of an entity is expressed using a specified unit of measurement.
-
D.
associatedWithFront
Indicates a relationship where one entity is linked or connected specifically to the front part, side, or face of another entity.
-
E.
associatedWithMatch
Indicates a relationship where an entity is linked or connected to a particular match or matching event.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df7fe9fc81908b3b8d1dc06a829c |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7fae088190973f70c69738af49 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 8:53 p.m.