Triple
T31544651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | red nucleus |
E804841
|
entity |
| Predicate | moreProminentIn |
P136851
|
FINISHED |
| Object | non-human mammals |
—
|
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: non-human mammals | Statement: [red nucleus, moreProminentIn, non-human mammals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: moreProminentIn Context triple: [red nucleus, moreProminentIn, non-human mammals]
-
A.
moreProminentSince
Indicates that one entity has become more prominent or noticeable relative to another entity starting from a specified point in time.
-
B.
gainedProminenceFor
Indicates that an entity became widely recognized or notable specifically because of another entity, action, or achievement.
-
C.
isOneOfMostProminentIn
chosen
Indicates that an entity ranks among the most notable, influential, or widely recognized members within a specified group, category, or domain.
-
D.
promotedIn
Indicates that an entity was advanced to a higher rank, position, or status during a specified time or event.
-
E.
isMostProminentIn
Indicates that an entity stands out as the most notable, influential, or dominant among comparable entities within a specified context or domain.
- 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_69f348d11a048190a65eb8384a3754ac |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8055f8081908f635fe04654b5fe |
completed | May 3, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:07 p.m.