Triple
T34723578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayangan Ifugao language |
E1000984
|
entity |
| Predicate | isInContactWith |
P181554
|
FINISHED |
| Object | Ilocano language |
—
|
NE NERFINISHED |
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: Ilocano language | Statement: [Ayangan Ifugao language, isInContactWith, Ilocano language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInContactWith Context triple: [Ayangan Ifugao language, isInContactWith, Ilocano language]
-
A.
hasContactState
Indicates that an entity is currently in a specific state or condition regarding its physical or communicative contact with another entity.
-
B.
hasContactInfluenceFrom
Indicates that one entity’s state, behavior, or properties are directly affected or altered through physical or direct contact with another entity.
-
C.
hasContactRole
Indicates that an entity serves in a specific role or capacity as a contact for another entity.
-
D.
hasKontakion
Indicates that an entity is associated with or possesses a specific kontakion, i.e., a particular liturgical hymn or chant.
-
E.
bodyContact
Indicates that two entities are in physical contact with each other via their bodies.
- 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_69f76daeb6e48190a4c9a6b0edc80f72 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f77ff804f08190b431a31e6179ace4 |
completed | May 3, 2026, 5:03 p.m. |
Created at: May 3, 2026, 3:59 p.m.