Triple
T25284668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yardley London |
E633903
|
entity |
| Predicate | hasSignatureNote |
P139293
|
FINISHED |
| Object | English lavender |
—
|
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: English lavender | Statement: [Yardley London, hasSignatureNote, English lavender]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignatureNote Context triple: [Yardley London, hasSignatureNote, English lavender]
-
A.
hasSignFor
Indicates that one entity displays, bears, or provides a sign, symbol, or notice that represents, directs attention to, or gives information about another entity.
-
B.
noteSignature
chosen
Indicates that one entity serves as a signature or identifying mark attached to a note created or associated with another entity.
-
C.
hasSignatureUse
Indicates that an entity is used as an official or primary signature or identifying mark for another entity.
-
D.
hasSign
Indicates that an entity possesses, displays, or is associated with a particular sign or symbol.
-
E.
hasSignatureConcept
Indicates that something is associated with or characterized by a defining concept that uniquely represents its core meaning or identity.
- 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 21, 2026, 1:19 p.m.