Triple
T36412810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of Merlin, Third Class |
E896925
|
entity |
| Predicate | classWithinOrderOfMerlin |
P141021
|
FINISHED |
| Object | third |
—
|
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: third | Statement: [Order of Merlin, Third Class, classWithinOrderOfMerlin, third]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classWithinOrderOfMerlin Context triple: [Order of Merlin, Third Class, classWithinOrderOfMerlin, third]
-
A.
asksOfArthur
Indicates that one entity poses a question or request specifically to Arthur.
-
B.
rankInSomeGrimoires
chosen
Indicates the hierarchical position or level assigned to something within at least one grimoire’s ranking system.
-
C.
من السور
Indicates a relationship where something originates from, is taken from, or is part of a specific wall or fence.
-
D.
associatedWithNobleOrder
Indicates that an entity has a formal or recognized connection to a noble order, such as membership, affiliation, or honorary association.
-
E.
compiledUnderReignOf
Indicates that something (such as a document, code, or work) was compiled or put together during the period when a particular ruler or authority was in power.
- 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:10 p.m.