Triple
T3690955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Growing Up in New Guinea |
E78340
|
entity |
| Predicate | hasMainCharacterType |
P20969
|
FINISHED |
| Object | Manus children |
—
|
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: Manus children | Statement: [Growing Up in New Guinea, hasMainCharacterType, Manus children]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainCharacterType Context triple: [Growing Up in New Guinea, hasMainCharacterType, Manus children]
-
A.
hasMainRole
Indicates that an entity holds the primary or most significant role in relation to another entity or context.
-
B.
protagonistType
chosen
Indicates the role or category that the main character (protagonist) of a story or scenario belongs to.
-
C.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
D.
mainCharactersAre
Indicates that the specified entities serve as the primary or central characters in a narrative or work.
-
E.
hasIconicCharacter
Indicates that something is associated with a character widely recognized as emblematic or highly representative of it.
- 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_69ad85e285a081908f8cbfa9e2ed9b75 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc4e6147c8190ae358e8cc94f479c |
completed | March 8, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69adb84dc5808190850aa6975cb09e27 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:26 p.m.