Triple
T18079438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book II (History of Animals) |
E432646
|
entity |
| Predicate | hasAuthorialMethod |
P129725
|
FINISHED |
| Object | comparative study of species |
—
|
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: comparative study of species | Statement: [Book II (History of Animals), hasAuthorialMethod, comparative study of species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuthorialMethod Context triple: [Book II (History of Animals), hasAuthorialMethod, comparative study of species]
-
A.
hasAuthor
Indicates that an entity is written or created by a specific author.
-
B.
hasAuthorOf
Indicates that one entity is the author or creator of another entity (such as a work, document, or publication).
-
C.
hasAuthorField
Indicates that an entity includes a designated field or attribute for specifying its author.
-
D.
hasAuthorConcept
Indicates that an entity is associated with a conceptual or abstract representation of its author, rather than a specific individual author instance.
-
E.
hasAuthorType
Indicates that an entity is associated with an author characterized by a specific role, category, or type.
- 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_69d8b907d05c819083cc3bd6021089e6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4d9f81ff08190b7465e3c5568aa59 |
completed | April 19, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69e3f90c652481908133a73106d78919 |
completed | April 18, 2026, 9:35 p.m. |
| PDg | Predicate description generation | batch_69e42d8eefa88190a700c7c1b4213e46 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:27 a.m.