Triple
T5632927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Notamacropus |
E147875
|
entity |
| Predicate | includesOrganismsWith |
P45064
|
FINISHED |
| Object | strong hind legs |
—
|
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: strong hind legs | Statement: [Notamacropus, includesOrganismsWith, strong hind legs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesOrganismsWith Context triple: [Notamacropus, includesOrganismsWith, strong hind legs]
-
A.
includesSpecies
Indicates that one entity contains or encompasses one or more species as part of its composition or scope.
-
B.
includesSpeciesFrom
Indicates that one collection, group, or set contains one or more species that originate from or belong to another specified source or context.
-
C.
containsModelOrganisms
Indicates that one entity includes or incorporates model organisms as part of its contents or composition.
-
D.
includesTaxaWith
chosen
Indicates that an entity contains or encompasses one or more specified taxa within its scope or membership.
-
E.
targetOrganism
Indicates that an action, process, or effect is directed toward or intended to impact a particular organism.
- 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_69c00907bc8881909ed760d3ed73ef35 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0225ff3248190b93c9f5887553fd4 |
completed | March 22, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69c01b1f12ec8190b4b9d9ee31cabe19 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.