Triple
T35759899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B6700 |
E1033542
|
entity |
| Predicate | controlStructureSupport |
P196313
|
FINISHED |
| Object | hardware support for procedure calls |
—
|
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: hardware support for procedure calls | Statement: [B6700, controlStructureSupport, hardware support for procedure calls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlStructureSupport Context triple: [B6700, controlStructureSupport, hardware support for procedure calls]
-
A.
controlStructure
Indicates a relationship where one entity governs, regulates, or directs the behavior, operation, or flow of another entity or process.
-
B.
typicalControlStructures
Indicates that the subject entity commonly governs or organizes the flow of execution or behavior of the object entity, as a standard or usual control mechanism.
-
C.
hasLoopOrBranch
Indicates that the referenced structure, process, or path contains at least one loop or branching point in its flow or topology.
-
D.
supportsConditionals
chosen
Indicates that one entity provides or enables the use of conditional constructs or conditional behavior for another entity.
-
E.
branchingPattern
Indicates the structural way in which one element divides into multiple offshoots or subdivisions from a common source.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fefa064ab48190925759950d0d94d9 |
completed | May 9, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69fef96ae5d08190b027435753c44821 |
completed | May 9, 2026, 9:07 a.m. |
Created at: May 3, 2026, 4:06 p.m.