Triple
T24837699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P2C2E House |
E621524
|
entity |
| Predicate | controlsProcess |
P11736
|
FINISHED |
| Object | maintenance of story streams |
—
|
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 of story streams | Statement: [P2C2E House, controlsProcess, maintenance of story streams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlsProcess Context triple: [P2C2E House, controlsProcess, maintenance of story streams]
-
A.
regulatesProcess
chosen
Indicates that one entity controls, modulates, or influences the occurrence, rate, or outcome of a process involving another entity.
-
B.
controlsSystem
Indicates that one entity has the authority or capability to direct, manage, or regulate the operation of a system.
-
C.
exportControl
Indicates that an entity is subject to rules or restrictions governing the transfer or export of goods, services, or information across borders.
-
D.
controlStatus
Indicates that one entity has a particular level, state, or condition of control over another entity or process.
-
E.
controlStand
Indicates that one entity manages, directs, or regulates the operation or behavior of another entity or system.
- 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_69e2fac185d48190a0a6073ad1f6b792 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 5:18 a.m.