Triple
T28616375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CreateSemaphore |
E724281
|
entity |
| Predicate | objectTypeCreated |
P64281
|
FINISHED |
| Object | semaphore object |
—
|
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: semaphore object | Statement: [CreateSemaphore, objectTypeCreated, semaphore object]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: objectTypeCreated Context triple: [CreateSemaphore, objectTypeCreated, semaphore object]
-
A.
createdEntityType
chosen
Indicates the type or category of entity that was produced or brought into existence as a result of the creation action.
-
B.
addsObjectType
Indicates that an entity introduces or includes a specific type of object into a collection, structure, or context.
-
C.
typicalObjectType
Indicates that something is a common or characteristic type of object typically associated with or involved in another entity or situation.
-
D.
objectUsed
Indicates that one entity is used as a tool, instrument, or resource in performing an action involving another entity.
-
E.
createdDocument
Indicates that an entity has produced or authored a specific document.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:32 a.m.