Triple
T25977983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petroica traversi |
E645991
|
entity |
| Predicate | keyIndividual |
P159624
|
FINISHED |
| Object | Old Blue (female black robin) |
—
|
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: Old Blue (female black robin) | Statement: [Petroica traversi, keyIndividual, Old Blue (female black robin)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyIndividual Context triple: [Petroica traversi, keyIndividual, Old Blue (female black robin)]
-
A.
keyPerson
Indicates that a person plays a primary, central, or critically important role in relation to an organization, project, or entity.
-
B.
keyTarget
Indicates that one entity serves as the primary focus, objective, or intended recipient of another entity’s action, function, or influence.
-
C.
keyMember
Indicates that an entity plays a central, highly important, or leading role within a group, organization, or structure.
-
D.
key
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
-
E.
keys
Indicates that one entity serves as a key (or set of keys) that can open, access, or control another entity.
- F. None of above. chosen
Provenance (4 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_69e77e8768648190b27bb578f14bcb88 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6050aa9948190a439fb09ff4e0ed1 |
completed | May 2, 2026, 2:07 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 22, 2026, 8:52 a.m.