Triple
T25513778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Endless Forms Most Beautiful |
E639449
|
entity |
| Predicate | titlePhraseOrigin |
P142073
|
FINISHED |
| Object | On the Origin of Species |
—
|
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: On the Origin of Species | Statement: [Endless Forms Most Beautiful, titlePhraseOrigin, On the Origin of Species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titlePhraseOrigin Context triple: [Endless Forms Most Beautiful, titlePhraseOrigin, On the Origin of Species]
-
A.
religiousPhraseOrigin
Indicates that one entity is the source, origin, or provenance of a particular religious phrase associated with another entity.
-
B.
sourceOfPhrase
chosen
Indicates that one entity is the origin or provider of a particular phrase used or referenced by another entity.
-
C.
titlePhrase
Indicates that one entity is a phrase functioning as the title or name of another entity.
-
D.
nameOriginExplanation
Indicates that an explanation is provided for the origin or derivation of a given name.
-
E.
historicalOriginMeaning
Indicates that one entity explains the original historical source or derivational meaning of another entity.
- 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_69e75dbe32e48190a62d749a0ff2a96a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 21, 2026, 2:54 p.m.