Triple
T9559370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pukapukan |
E230627
|
entity |
| Predicate | secondaryUsage |
P23955
|
FINISHED |
| Object | cultural and traditional practices |
—
|
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: cultural and traditional practices | Statement: [Pukapukan, secondaryUsage, cultural and traditional practices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryUsage Context triple: [Pukapukan, secondaryUsage, cultural and traditional practices]
-
A.
secondaryFunction
Indicates that an entity has an additional, supporting role or purpose beyond its primary function.
-
B.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
C.
secondaryActivity
Indicates that an entity engages in an additional, non-primary activity or role alongside its main activity.
-
D.
secondaryLandUse
chosen
Indicates a secondary or additional way in which a piece of land is used, beyond its primary designated use.
-
E.
secondarySee
Indicates that one entity is referenced as an additional or alternative point of consultation or viewing in relation to another entity.
- 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_69ca847e53a88190a60eed7e02257f10 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd994a7e9c8190b68883c2ea45aa1a |
completed | April 1, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69ccd594d0ac8190a81bc11a3a538167 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:03 p.m.