Triple
T29627954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | love-in-idleness |
E755195
|
entity |
| Predicate | hasOtherCommonName |
P65979
|
FINISHED |
| Object | heartsease |
—
|
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: heartsease | Statement: [love-in-idleness, hasOtherCommonName, heartsease]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOtherCommonName Context triple: [love-in-idleness, hasOtherCommonName, heartsease]
-
A.
includesCommonName
Indicates that one entity contains or specifies a commonly used (non-scientific) name for another entity.
-
B.
otherCommonName
chosen
Indicates that an entity is known by an additional, alternative common name besides its primary one.
-
C.
commonName
Indicates that one entity is the commonly used or vernacular name by which the other entity is known.
-
D.
commonNameDerivedFrom
Indicates that the commonly used name of one entity originates from, or is derived based on, another entity.
-
E.
belongsToFamilyCommonName
Indicates that an entity is associated with, or classified under, a particular family-level common name.
- 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_69f0ef86b6ec8190a87fff07fd983b1e |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66e61866881908f1497a7ceb782bc |
completed | May 2, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:39 p.m.