Triple
T33551217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guldet blev till sand |
E859335
|
entity |
| Predicate | hasStageOrchestration |
P199707
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Guldet blev till sand, hasStageOrchestration, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStageOrchestration Context triple: [Guldet blev till sand, hasStageOrchestration, yes]
-
A.
hasOrchestration
Indicates that one entity coordinates, manages, or sequences the actions or interactions of another entity or set of entities.
-
B.
hasOrchestrationBy
Indicates that something is organized, coordinated, or arranged by a specified agent or entity.
-
C.
hasOrchestrationCompletedBy
Indicates that an orchestration process has been fully completed by a specified agent or system.
-
D.
hasStageIn
Indicates a relationship where one entity occurs, exists, or takes place within a particular stage or phase of another process, lifecycle, or sequence.
-
E.
usesOrchestration
Indicates that one entity employs orchestration mechanisms or tools to coordinate, manage, or automate the behavior and interactions of other entities or processes.
- 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_69f3497b2b68819093207971b5e13dc8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff519b65f081909902ba83b775ef85 |
completed | May 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69ff506fccdc8190bd93269589040aed |
completed | May 9, 2026, 3:19 p.m. |
| PDg | Predicate description generation | batch_69ff519a67008190b1eda931fdeff53e |
completed | May 9, 2026, 3:24 p.m. |
Created at: May 1, 2026, 1:39 a.m.