Triple
T36872570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | typing.NewType |
E911260
|
entity |
| Predicate | hasNoRuntimeOverhead |
P205093
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [typing.NewType, hasNoRuntimeOverhead, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoRuntimeOverhead Context triple: [typing.NewType, hasNoRuntimeOverhead, true]
-
A.
hasOverheadType
Indicates that one entity is associated with a specific category or type of overhead (such as cost, resource, or operational overhead) that applies to it.
-
B.
hasLineOverhead
Indicates that one entity has an overhead line (such as a cable, wire, or similar linear infrastructure) positioned above it or running over it.
-
C.
hasRuntimeType
Indicates that an entity is of, or conforms to, a specific type when evaluated at runtime rather than at compile time.
-
D.
hasSectionOverhead
Indicates that one entity includes or is associated with an overhead section of another entity.
-
E.
hasSmallMemoryFootprint
Indicates that something requires only a small amount of memory resources to operate or be stored.
- 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:13 p.m.