Triple
T34286965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allen |
E879764
|
entity |
| Predicate | controlSystemProperty |
P123498
|
FINISHED |
| Object | no central world model |
—
|
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: no central world model | Statement: [Allen, controlSystemProperty, no central world model]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlSystemProperty Context triple: [Allen, controlSystemProperty, no central world model]
-
A.
controlsSystem
Indicates that one entity has the authority or capability to direct, manage, or regulate the operation of a system.
-
B.
controlParameter
chosen
Indicates that one entity functions as a parameter that governs, tunes, or constrains the behavior or operation of another entity.
-
C.
controlApp
Indicates that one entity has the ability or authority to operate, manage, or direct the behavior of an application.
-
D.
propertyControl
Indicates that one entity has authority over, manages, or directs the use and disposition of another entity’s property.
-
E.
controlLink
Indicates a relationship where one entity exerts control, influence, or governing authority over another entity or process.
- 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_69f349b6df1c81908e5e5b6c2ab6409b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69feabcda59481908f2bc13b46fcced1 |
completed | May 9, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69feaabd63f88190b30dcf6dd2ea39d1 |
completed | May 9, 2026, 3:32 a.m. |
Created at: May 1, 2026, 1:57 a.m.