Triple
T35602889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linktrace Message |
E1028802
|
entity |
| Predicate | scopeControlledBy |
P53029
|
FINISHED |
| Object | maintenance domain level |
—
|
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: maintenance domain level | Statement: [Linktrace Message, scopeControlledBy, maintenance domain level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scopeControlledBy Context triple: [Linktrace Message, scopeControlledBy, maintenance domain level]
-
A.
scopeOfControl
Indicates the extent or range within which an entity has authority, influence, or control over another entity or set of entities.
-
B.
rangeControlledBy
chosen
Indicates that the extent or scope of something is regulated, limited, or determined by another entity.
-
C.
isControlledUnder
Indicates that one entity is subject to regulatory, legal, or authoritative control exercised by another entity or governing framework.
-
D.
recognizedControlOf
Indicates that one entity has formally acknowledged and accepted another entity’s authority or control over something.
-
E.
controlsOrControlled
Indicates that one entity has control over another entity or is itself under the control of that other entity.
- 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_69f76e0653ec81909b1b813c126c6574 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec411908190857785f69d6d6d7a |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.