Triple
T19987519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NES-101 |
E493971
|
entity |
| Predicate | controllerShape |
P138218
|
FINISHED |
| Object | dogbone |
—
|
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: dogbone | Statement: [NES-101, controllerShape, dogbone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controllerShape Context triple: [NES-101, controllerShape, dogbone]
-
A.
controlsType
Indicates that one entity has authority over, or the ability to direct or regulate, the type or category of another entity.
-
B.
coreShape
Indicates that one entity serves as the primary or central shape or geometric form of another entity.
-
C.
controlFrom
Indicates that one entity exercises authority, influence, or regulatory power over another entity or process.
-
D.
inputShape
Indicates the geometric form or configuration that is provided as input to a process, function, or system.
-
E.
controlLayout
Indicates that one entity determines or manages the spatial or structural arrangement of another entity.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65fdd1a5c8190af756632aac38bf4 |
completed | April 20, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 11, 2026, 3:29 p.m.