Triple
T35015352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Enchiridion |
E1010038
|
entity |
| Predicate | activatedWith |
P153946
|
FINISHED |
| Object | gems of the princesses |
—
|
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: gems of the princesses | Statement: [The Enchiridion, activatedWith, gems of the princesses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activatedWith Context triple: [The Enchiridion, activatedWith, gems of the princesses]
-
A.
activatedFor
Indicates that something has been enabled, triggered, or made operational specifically on behalf of or in the context of a particular entity or target.
-
B.
activatedAs
Indicates that one entity has been put into an active or operational state in the role or capacity of another specified entity.
-
C.
activeWith
chosen
Indicates that an entity is currently engaged in or functioning together with another specified entity.
-
D.
activationBy
Indicates that one entity initiates, triggers, or enhances the activity, function, or state of another entity.
-
E.
activeAt
Indicates that an entity is functioning, valid, or in effect during a specified time or at a particular location or context.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:01 p.m.