Triple
T38583022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highmountain tauren |
E932286
|
entity |
| Predicate | requiresUnlock |
P202774
|
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: [Highmountain tauren, requiresUnlock, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresUnlock Context triple: [Highmountain tauren, requiresUnlock, Yes]
-
A.
requiresLock
Indicates that performing the associated action or accessing the related resource is contingent on acquiring a lock to ensure exclusive or synchronized use.
-
B.
requiresPass
Indicates that access to or participation in something is conditional on possessing a valid pass.
-
C.
requiresToAccess
Indicates that one entity must be obtained, satisfied, or fulfilled in order to gain access to another entity.
-
D.
requiresSeal
Indicates that one entity must be sealed or have a seal applied as a necessary condition for another entity’s use, validity, or completion.
-
E.
usesLockSystem
Indicates that one entity employs or relies on a locking mechanism or lock-based system provided by another entity.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00b6e163308190adeb1d6eb8558641 |
completed | May 10, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_6a00b67e0e388190b08ad66cee4cb0d7 |
completed | May 10, 2026, 4:46 p.m. |
| PDg | Predicate description generation | batch_6a00b6e0b954819094e63589d718b9af |
completed | May 10, 2026, 4:48 p.m. |
Created at: May 3, 2026, 4:32 p.m.