Triple
T24472421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tinikling |
E617136
|
entity |
| Predicate | tiklingRefersTo |
P156235
|
FINISHED |
| Object | a type of rail bird |
—
|
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: a type of rail bird | Statement: [Tinikling, tiklingRefersTo, a type of rail bird]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tiklingRefersTo Context triple: [Tinikling, tiklingRefersTo, a type of rail bird]
-
A.
refersSpecificallyTo
Indicates that one entity makes an explicit, precise reference to another particular entity, distinguishing it from more general or ambiguous references.
-
B.
refersToCharacter
Indicates that one entity makes reference to, mentions, or points to a specific character as its subject.
-
C.
tikanga
Indicates the culturally appropriate, customary, or correct way of doing things within a particular social or cultural context.
-
D.
notablyRefersTo
Indicates that one entity makes a particularly significant or noteworthy reference to another entity, beyond a routine or incidental mention.
-
E.
referredTo
Indicates that one entity has mentioned, directed attention to, or cited another entity as a point of reference.
- 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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29944bea081908f8a732495d67cfc |
completed | April 29, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:20 a.m.