Triple
T9029778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G.fast |
E216138
|
entity |
| Predicate | optimizedForLoopLength |
P85771
|
FINISHED |
| Object | below 100 meters for highest speeds |
—
|
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: below 100 meters for highest speeds | Statement: [G.fast, optimizedForLoopLength, below 100 meters for highest speeds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: optimizedForLoopLength Context triple: [G.fast, optimizedForLoopLength, below 100 meters for highest speeds]
-
A.
instructionLength
Indicates the duration or amount of time required to carry out a given instruction or operation.
-
B.
optimizationLevel
Indicates the degree or intensity to which a process, system, or solution has been refined to improve its performance or efficiency.
-
C.
approximateBlockLength
Indicates that one entity specifies or estimates the length of a block in an approximate or non-exact manner.
-
D.
jumpLength
Indicates the distance covered by an entity in a single jump.
-
E.
loopType
Indicates the specific kind or category of loop structure or iteration pattern used in a process or control flow.
- F. None of above. chosen
Provenance (4 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a9bcb508190b58751f1772407d4 |
completed | April 1, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee3597c81908919cf866ae95c24 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f6dec4081909379bd57c02a5710 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:08 p.m.