Triple
T27223779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mehinaku people |
E681351
|
entity |
| Predicate | notableAnthropologists |
P185613
|
FINISHED |
| Object | Thomas Gregor |
—
|
NE NERFINISHED |
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: Thomas Gregor | Statement: [Mehinaku people, notableAnthropologists, Thomas Gregor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAnthropologists Context triple: [Mehinaku people, notableAnthropologists, Thomas Gregor]
-
A.
notableResearchers
Indicates that the subject has researchers who are particularly distinguished or recognized in their field associated with it.
-
B.
notableIndividuals
chosen
Indicates that certain individuals are recognized as particularly important, famous, or influential in relation to something.
-
C.
notableTheorist
Indicates that the subject is recognized as a significant or influential theorist in relation to the object or specified field.
-
D.
notableResearcherGroup
Indicates that an entity is a prominent or distinguished member of a particular group of researchers.
-
E.
notableScientist
Indicates that the subject is a scientist who is widely recognized for significant contributions or impact in their field.
- 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_69eefac9f64c8190a07490fe0c8b72a3 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69ffa9677be08190852c8ef6c2545fed |
completed | May 9, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69ffa6570e2c8190a9d7b37f12b91d9a |
completed | May 9, 2026, 9:25 p.m. |
Created at: April 27, 2026, 9:43 a.m.