Triple
T10431585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hold Up |
E245925
|
entity |
| Predicate | containsInterpolationOf |
P82103
|
FINISHED |
| Object | Maps |
—
|
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: Maps | Statement: [Hold Up, containsInterpolationOf, Maps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsInterpolationOf Context triple: [Hold Up, containsInterpolationOf, Maps]
-
A.
usesInterpolationFrom
Indicates that one entity derives or computes its values by applying interpolation based on data or parameters obtained from another entity.
-
B.
hasNotableInterpolationIn
chosen
Indicates that one entity contains a significant or noteworthy interpolation, insertion, or embedded segment within the other entity.
-
C.
hasInterpolation
Indicates that one value, state, or representation is derived from others by applying an interpolation method between them.
-
D.
hasIntercalation
Indicates that an entity includes or undergoes the insertion of additional elements (such as units, segments, or periods) into an existing ordered sequence or structure.
-
E.
interpolationOf
Indicates that one entity is derived by estimating intermediate values between known data points of another entity.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea63f03c81908331655241102725 |
completed | April 7, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_69d4dfbc546881908f312c66ee195f79 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:13 p.m.