Triple
T18588734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sword of Gryffindor |
E454303
|
entity |
| Predicate | unlockedBy |
P25726
|
FINISHED |
| Object | acts of great courage |
—
|
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: acts of great courage | Statement: [Sword of Gryffindor, unlockedBy, acts of great courage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unlockedBy Context triple: [Sword of Gryffindor, unlockedBy, acts of great courage]
-
A.
unveiledBy
Indicates that something (such as an object, artwork, or project) was formally revealed or presented to the public by a particular agent or entity.
-
B.
releaseObtainedBy
Indicates that a particular release results from, or is produced through, a specified obtaining or acquisition process.
-
C.
unlockBehavior
Indicates that one entity enables access to or activates the behavior, functionality, or state of another entity.
-
D.
wasUncoveredBy
Indicates that something previously hidden, unknown, or concealed became revealed or discovered through the actions or efforts of a particular agent or process.
-
E.
canBeOpenedBy
chosen
Indicates that one entity has the ability or permission to open another entity.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e545b3e564819088e60fc25d1976f0 |
completed | April 19, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:44 a.m.