Triple
T37649882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KK |
E937142
|
entity |
| Predicate | guidesPlayerIn |
P18444
|
FINISHED |
| Object | use of ethereal weaving |
—
|
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: use of ethereal weaving | Statement: [KK, guidesPlayerIn, use of ethereal weaving]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guidesPlayerIn Context triple: [KK, guidesPlayerIn, use of ethereal weaving]
-
A.
guidesAudienceThroughAction
Indicates that one entity leads or directs an audience step-by-step through performing a specific action or process.
-
B.
guidesCharactersToward
Indicates a relationship in which one entity directs, influences, or leads characters toward a particular goal, destination, or outcome.
-
C.
guidedBy
Indicates that an entity’s actions, decisions, or movement are directed, advised, or led by another entity.
-
D.
guidanceRole
Indicates a relationship where one entity provides direction, advice, or mentorship to another in a guiding capacity.
-
E.
providesGuidanceTo
chosen
Indicates that one entity offers direction, advice, or instruction to 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_69f76ed4fe908190b8061c5c135e0971 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa1321b48190af92a3e7ec24ec5b |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.