Triple
T29911264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SCNLight |
E759679
|
entity |
| Predicate | canBeAttachedTo |
P10139
|
FINISHED |
| Object | SCNNode |
—
|
NE NERFINISHED |
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: SCNNode | Statement: [SCNLight, canBeAttachedTo, SCNNode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeAttachedTo Context triple: [SCNLight, canBeAttachedTo, SCNNode]
-
A.
canBeAddedTo
Indicates that one entity is capable of being combined or incorporated with another entity, typically without conflict or incompatibility.
-
B.
canBeEmbeddedIn
Indicates that one entity can be inserted or integrated within another entity, typically preserving structure or compatibility.
-
C.
attachedTo
chosen
Indicates that one entity is physically or logically fastened, connected, or joined to another entity.
-
D.
canBeAdaptedBy
Indicates that one entity is capable of being modified, adjusted, or tailored for use by another entity.
-
E.
canBelongTo
Indicates that something is capable of being a member or part of a particular group, category, or owner.
- 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_69f224600590819085e148a01c056ef6 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: April 29, 2026, 6:10 p.m.