Triple
T4606439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lumad |
E100447
|
entity |
| Predicate | landRelation |
P57406
|
FINISHED |
| Object | strong spiritual ties to ancestral lands |
—
|
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: strong spiritual ties to ancestral lands | Statement: [Lumad, landRelation, strong spiritual ties to ancestral lands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landRelation Context triple: [Lumad, landRelation, strong spiritual ties to ancestral lands]
-
A.
arealRelation
Indicates a spatial relationship between areas, such as overlap, containment, adjacency, or relative positioning between two regions.
-
B.
landComponent
Indicates that one entity is a physical land portion or segment that forms part of a larger land area or land-related whole.
-
C.
typeOfMunicipalRelationship
Indicates a formal type or category of administrative or cooperative relationship that exists between municipalities.
-
D.
relationshipBetweenHouses
Indicates a relational connection or association that exists between two or more houses.
-
E.
titleRelation
Indicates a relationship where one entity serves as the title, designation, or formal name associated with another entity.
- 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_69bd43cce1e08190a07d53af6a9b6c24 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd599c50d08190ab226cd0691e29f9 |
completed | March 20, 2026, 2:28 p.m. |
| PD | Predicate disambiguation | batch_69bd522e2d5c8190937d0b5574f78f99 |
completed | March 20, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69bd56b5f4648190834eafa666d53caa |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:12 p.m.