Triple
T33029351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Direct Client-to-Client |
E845120
|
entity |
| Predicate | oftenControlledBy |
P192390
|
FINISHED |
| Object | IRC client settings |
—
|
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: IRC client settings | Statement: [Direct Client-to-Client, oftenControlledBy, IRC client settings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenControlledBy Context triple: [Direct Client-to-Client, oftenControlledBy, IRC client settings]
-
A.
isUnderControlOf
Indicates that one entity is subject to the authority, direction, or governance of another entity.
-
B.
isControlledUnder
Indicates that one entity is subject to regulatory, legal, or authoritative control exercised by another entity or governing framework.
-
C.
endedControlOf
Indicates that one entity has ceased to exercise authority, influence, or governance over another entity or domain.
-
D.
exertsControlOver
Indicates that one entity has the power or authority to direct, influence, or determine the actions or decisions of another entity.
-
E.
oppositeControlledBy
Indicates that one entity is under the control or influence of another entity that is positioned or defined as its opposite or counterpart.
- 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_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69fd098357348190a835c0b6d99857d2 |
completed | May 7, 2026, 9:52 p.m. |
Created at: May 1, 2026, 1:24 a.m.