Triple
T12274789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birdman ritual |
E292560
|
entity |
| Predicate | periodOfPractice |
P104183
|
FINISHED |
| Object | late pre-contact period |
—
|
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: late pre-contact period | Statement: [Birdman ritual, periodOfPractice, late pre-contact period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodOfPractice Context triple: [Birdman ritual, periodOfPractice, late pre-contact period]
-
A.
regionOfPractice
Indicates the geographic area or jurisdiction in which an entity regularly conducts its professional activities or services.
-
B.
partOfProfessionalPracticeOf
Indicates that something is a component or integral element of a particular professional’s regular practice or work activities.
-
C.
practicedInField
Indicates that an entity has engaged in practical work, training, or professional activity within a specified field or domain.
-
D.
practicedMedicineIn
Indicates that a person engaged in the professional practice of medicine within a specified location or jurisdiction.
-
E.
practiceType
Indicates the specific kind or category of practice associated with an entity or activity.
- 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_69d6ab6856488190b5d31178d5015f8e |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d9380a5e78819086bd4dfe9a83d1f5 |
completed | April 10, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69d91c4a66cc819083ce6fcaf5042af6 |
completed | April 10, 2026, 3:50 p.m. |
| PDg | Predicate description generation | batch_69d93805cee08190a532ebcf5908e617 |
completed | April 10, 2026, 5:48 p.m. |
Created at: April 8, 2026, 9:52 p.m.