Triple
T10158765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DCC |
E233834
|
entity |
| Predicate | operatesOutside |
P26656
|
FINISHED |
| Object | IRC server message routing |
—
|
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 server message routing | Statement: [DCC, operatesOutside, IRC server message routing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesOutside Context triple: [DCC, operatesOutside, IRC server message routing]
-
A.
operatedOutside
Indicates that an entity performed operations or activities beyond a defined boundary, jurisdiction, or designated area.
-
B.
operatedOutsideControlOf
Indicates that an entity carried out actions or operations without being directed, supervised, or governed by another specified authority or controlling party.
-
C.
operatesWithin
Indicates that one entity carries out its activities, functions, or operations inside the scope, boundaries, or jurisdiction defined by another entity.
-
D.
operatesOver
Indicates that one entity performs actions or exerts functional control across, upon, or throughout another entity or domain.
-
E.
alsoOperatesIn
chosen
Indicates that an entity, in addition to its primary location or domain, conducts operations or activities in another specified place or context.
- 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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec56d944819081bc6ea36c905ba2 |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba795808190acc9124c98c6e40f |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:09 p.m.