Triple
T29911128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SCNMaterial |
E759677
|
entity |
| Predicate | canBeSharedBetween |
P193251
|
FINISHED |
| Object | multiple SCNGeometry instances |
—
|
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: multiple SCNGeometry instances | Statement: [SCNMaterial, canBeSharedBetween, multiple SCNGeometry instances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeSharedBetween Context triple: [SCNMaterial, canBeSharedBetween, multiple SCNGeometry instances]
-
A.
canBeShared
Indicates that something is capable of being distributed or accessed by multiple parties.
-
B.
canBeSharedTo
Indicates that something is capable of being shared or distributed to a particular recipient or destination.
-
C.
isShared
Indicates that something is jointly used, possessed, or made accessible by more than one entity.
-
D.
isSharedBy
Indicates that something is jointly possessed, used, or experienced by two or more entities.
-
E.
isSometimesShared
Indicates that an entity is occasionally or intermittently shared with others, rather than being exclusively owned or always shared.
- 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_69f224600590819085e148a01c056ef6 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
| PDg | Predicate description generation | batch_69fd3d45ccb8819082f15e60bd33afc9 |
completed | May 8, 2026, 1:32 a.m. |
Created at: April 29, 2026, 6:10 p.m.