Triple
T10316862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Men of Men |
E242038
|
entity |
| Predicate | peopleGroupType |
P42493
|
FINISHED |
| Object | Indigenous people of the United States |
—
|
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: Indigenous people of the United States | Statement: [Men of Men, peopleGroupType, Indigenous people of the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peopleGroupType Context triple: [Men of Men, peopleGroupType, Indigenous people of the United States]
-
A.
peopleType
chosen
Indicates the classification or category of people an entity is associated with or represents.
-
B.
peopleGroupWithin
Indicates that one group of people is geographically or organizationally contained within another group of people.
-
C.
peopleGroupOf
Indicates that one entity is a group or collection composed of the people represented by the other entity.
-
D.
typicalGroup
Indicates that the subject belongs to or represents a standard, characteristic, or commonly occurring group associated with the object.
-
E.
participantType
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
- 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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f4f354819080b4ed4bc61bdff6 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:49 a.m.