Triple
T7935894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VGA |
E184287
|
entity |
| Predicate | verticalSyncSignal |
P25707
|
FINISHED |
| Object | TTL-level signal |
—
|
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: TTL-level signal | Statement: [VGA, verticalSyncSignal, TTL-level signal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: verticalSyncSignal Context triple: [VGA, verticalSyncSignal, TTL-level signal]
-
A.
verticalOrder
Indicates that one entity is positioned directly above or below another along a vertical axis, establishing their relative vertical arrangement.
-
B.
synchronizesWith
chosen
Indicates that two or more entities coordinate their states or activities so that they occur in step or remain temporally consistent with each other.
-
C.
targetVertical
Indicates that one entity is directed toward, aligned with, or intended for a specific vertical market, domain, or industry segment.
-
D.
synchronizationBoundary
Indicates a point or condition at which concurrent or distributed processes must align or coordinate their states or actions to maintain consistency.
-
E.
verticalExtent
Indicates the total height or vertical span of an entity or region from its lowest to highest point.
- 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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3aede3cc81908b0d3b54e68997b9 |
completed | March 31, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69cae9335f288190ba96781fd6576a2b |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:08 p.m.