Triple
T28463417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanunoo Mangyan |
E720220
|
entity |
| Predicate | ambahanCharacteristics |
P128001
|
FINISHED |
| Object | heptasyllabic verse |
—
|
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: heptasyllabic verse | Statement: [Hanunoo Mangyan, ambahanCharacteristics, heptasyllabic verse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ambahanCharacteristics Context triple: [Hanunoo Mangyan, ambahanCharacteristics, heptasyllabic verse]
-
A.
catalogCharacteristic
Indicates that a catalog has a specific characteristic or attribute associated with it.
-
B.
ruleCharacteristics
Indicates the defining properties, constraints, or parameters that specify how a particular rule operates or should be applied.
-
C.
providesAdditionalCharactersFor
Indicates that one entity supplies extra or supplementary characters to be used by another entity or process.
-
D.
spanCharacteristic
Indicates that one entity has a particular measurable or descriptive property that characterizes the extent, duration, or range of another entity or phenomenon.
-
E.
entityCharacteristic
chosen
Indicates that an entity possesses, exhibits, or is defined by a particular characteristic or attribute.
- 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_69f01a58a67c819097936d9e8da8d6e6 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64ea7a0b48190ae49504aad5b375b |
completed | May 2, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 2:42 a.m.