Triple
T37920067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redbone Coonhound |
E945927
|
entity |
| Predicate | commonColorFault |
P115452
|
FINISHED |
| Object | large white markings |
—
|
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: large white markings | Statement: [Redbone Coonhound, commonColorFault, large white markings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonColorFault Context triple: [Redbone Coonhound, commonColorFault, large white markings]
-
A.
hasColorIssues
chosen
Indicates that an entity exhibits problems, defects, or inconsistencies related to its color or coloration.
-
B.
colors
Indicates that one entity assigns, describes, or provides the color or colors of another entity.
-
C.
reportedColor
Indicates that one entity has stated, described, or recorded the color attribute of another entity.
-
D.
cereColor
Indicates that one entity specifies or denotes the color of another entity’s cere (the fleshy area above a bird’s beak).
-
E.
hasFanColor
Indicates that an entity (typically a fan or fan-like object) possesses a specific color attribute.
- 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_69f76ef2ebd88190be5229f2621070b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff64b957bc81908afbc5914234a8ea |
completed | May 9, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69ff6446593c81909173e296eea2590c |
completed | May 9, 2026, 4:43 p.m. |
Created at: May 3, 2026, 4:20 p.m.