Triple
T5027253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LVO |
E113205
|
entity |
| Predicate | notDependentOn |
P38907
|
FINISHED |
| Object | ministerial advice |
—
|
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: ministerial advice | Statement: [LVO, notDependentOn, ministerial advice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notDependentOn Context triple: [LVO, notDependentOn, ministerial advice]
-
A.
doesNotDependOn
chosen
Indicates that one entity’s state, behavior, or outcome is completely independent of, and not influenced or determined by, another entity.
-
B.
independenceFrom
Indicates that one entity is not controlled, governed, or significantly influenced by another entity.
-
C.
isIndependent
Indicates that an entity exists, functions, or operates without being controlled, influenced, or determined by another entity.
-
D.
notStandalone
Indicates that an entity cannot exist, function, or be valid independently and must be associated with or supported by another entity.
-
E.
doesNotDetermine
Indicates that one entity or factor does not uniquely fix, decide, or specify the state, value, or outcome of another.
- 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_69bd443775e48190a646ffbfc4334723 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd738d852c8190a122354f1e1f5343 |
completed | March 20, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69bd71509e9c8190a60c1d8d04936a12 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:36 p.m.