Triple
T21042312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacu jawi |
E518355
|
entity |
| Predicate | animalHarnessing |
P42189
|
FINISHED |
| Object | pair of cows yoked together |
—
|
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: pair of cows yoked together | Statement: [Pacu jawi, animalHarnessing, pair of cows yoked together]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: animalHarnessing Context triple: [Pacu jawi, animalHarnessing, pair of cows yoked together]
-
A.
companionAnimals
Indicates a relationship where one entity keeps or cares for another entity as a pet or companion animal.
-
B.
usesCaninesFor
Indicates a relationship where an entity employs or relies on its canine teeth for a particular function or activity.
-
C.
involvedAnimal
Indicates that an animal participates in, is affected by, or is otherwise directly connected to the event or situation described.
-
D.
animalAssociation
chosen
Indicates a relationship in which one animal is associated with another animal or entity, such as through interaction, co-occurrence, or ecological linkage.
-
E.
hasAnimal
Indicates that one entity possesses, keeps, or is associated with an animal.
- 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_69e0b50438e08190917e2538bb8bc034 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fcf0b27881909d1c5b58be387a74 |
completed | April 21, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf6728881908a2a43a5c8804a2a |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:15 p.m.