Triple
T30144843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murchunga |
E766226
|
entity |
| Predicate | requiresDirectContactWith |
P70620
|
FINISHED |
| Object | player’s teeth or lips |
—
|
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: player’s teeth or lips | Statement: [Murchunga, requiresDirectContactWith, player’s teeth or lips]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresDirectContactWith Context triple: [Murchunga, requiresDirectContactWith, player’s teeth or lips]
-
A.
requiresCaredForPersonToReceive
Indicates that one entity’s receipt of something is conditional on a specific cared-for person also receiving it.
-
B.
requiresControlOf
Indicates that one entity must have control over another entity or resource as a prerequisite for some condition, action, or state to hold.
-
C.
requiresCare
Indicates that one entity depends on another to provide care, attention, or maintenance for its proper functioning or well-being.
-
D.
mustTouch
chosen
Indicates that the entities are required to be in direct physical contact with each other.
-
E.
requiresParticipationOf
Indicates that one entity’s occurrence, validity, or completion depends on the active involvement or participation of 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: April 29, 2026, 7:18 p.m.