Triple
T7694990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ponginae |
E174345
|
entity |
| Predicate | notableExtantMembers |
P33585
|
FINISHED |
| Object | Bornean orangutan |
—
|
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: Bornean orangutan | Statement: [Ponginae, notableExtantMembers, Bornean orangutan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableExtantMembers Context triple: [Ponginae, notableExtantMembers, Bornean orangutan]
-
A.
hasNotableMember
Indicates that a group, organization, or collection includes at least one member who is distinguished or noteworthy in some significant way.
-
B.
notablePersonnel
Indicates that the subject has associated individuals who are particularly important, distinguished, or prominent in relation to it.
-
C.
notableMemberOfRoster
Indicates that an entity is a distinguished or prominent member within a particular roster or lineup.
-
D.
notableConstituent
Indicates that one entity is a significant or prominent component, part, or member of another entity.
-
E.
hasExtantMembers
chosen
Indicates that the referenced group, category, or lineage currently has living or existing members.
- 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_69c6995966348190939e6c37ba272c06 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c706d1f0208190bc5b695aa5736244 |
completed | March 27, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69c70163dea88190ae729df50e63dfd7 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:02 p.m.