Triple
T9947403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Excalibur |
E195238
|
entity |
| Predicate | thematicMotif |
P39719
|
FINISHED |
| Object | knight |
—
|
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: knight | Statement: [The Excalibur, thematicMotif, knight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thematicMotif Context triple: [The Excalibur, thematicMotif, knight]
-
A.
thematicConcept
Indicates that one entity embodies, expresses, or is centrally concerned with a particular underlying theme or conceptual idea represented by the other entity.
-
B.
thematicFunction
Indicates how an entity participates in or contributes to the role structure of an event or situation (e.g., as agent, patient, instrument, etc.).
-
C.
thematicMaterial
chosen
Indicates that one entity serves as the primary recurring idea, motif, or thematic content that is developed or referenced by another entity.
-
D.
themeInspiration
Indicates that one entity serves as the creative source or conceptual basis that inspires or shapes the theme expressed in another entity.
-
E.
theme
Indicates the entity that is the primary participant or content affected or characterized by an action, event, or state.
- 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_69ca82e96a108190932bd1fc4acd73a0 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb657b35c81909448e93999f6e77c |
completed | April 2, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69cd1d97c44081908730071269f07712 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:45 p.m.