Triple
T33027723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NLST |
E845086
|
entity |
| Predicate | initiatedOver |
P186392
|
FINISHED |
| Object | control connection |
—
|
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: control connection | Statement: [NLST, initiatedOver, control connection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initiatedOver Context triple: [NLST, initiatedOver, control connection]
-
A.
initiatedIn
Indicates that an action, process, or event was started or first brought into effect within a specified context, such as a place, time, or situation.
-
B.
initiatedAfter
Indicates that one event or process begins only after another specified event or process has already started or occurred.
-
C.
initiatedBecauseOf
Indicates that one event, action, or process was started as a direct result of, or in response to, another specified cause or condition.
-
D.
initiatedBy
Indicates that an action, event, or process was started or set in motion by a particular entity.
-
E.
hasInitiation
Indicates that one entity initiates, starts, or triggers an action, process, or relationship involving another entity.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7cec398ac819081c954a993c323ee |
completed | May 3, 2026, 10:40 p.m. |
Created at: May 1, 2026, 1:23 a.m.