Triple
T35844336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lymphad |
E1036167
|
entity |
| Predicate | oftenTinctured |
P188809
|
FINISHED |
| Object | sable |
—
|
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: sable | Statement: [Lymphad, oftenTinctured, sable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenTinctured Context triple: [Lymphad, oftenTinctured, sable]
-
A.
typicalTincture
Indicates that something has the usual or standard tincture (coloring or hue) typically associated with it.
-
B.
tinctureOrdinary
Indicates that an ordinary (a basic heraldic shape or charge) is depicted with a specific tincture (color, metal, or fur) in a coat of arms.
-
C.
tinctureOfPale
Indicates that one entity is a tincture (medicinal or alcoholic extract) derived from or characterized by the pale aspect, quality, or component of another entity.
-
D.
tinctureOfSun
Indicates a relationship where something is infused, colored, or imbued with the qualities or essence symbolically associated with the sun.
-
E.
usesTincture
chosen
Indicates that one entity employs or applies a tincture in relation to another entity or context.
- 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_69f76e1a29e8819088280f26096aeb55 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fdd07a34c08190982b8c61c2775cf6 |
completed | May 8, 2026, noon |
| PD | Predicate disambiguation | batch_69fdbd25c7908190b72fca8de7ce503f |
completed | May 8, 2026, 10:38 a.m. |
Created at: May 3, 2026, 4:06 p.m.