Triple
T25624080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sumba pony |
E642380
|
entity |
| Predicate | hasCroup |
P162593
|
FINISHED |
| Object | sloping croup |
—
|
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: sloping croup | Statement: [Sumba pony, hasCroup, sloping croup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCroup Context triple: [Sumba pony, hasCroup, sloping croup]
-
A.
hasCP
Indicates that an entity possesses, is associated with, or is characterized by a specific CP (such as a control point, contact person, or configuration parameter), depending on the domain context.
-
B.
hasChorusIn
Indicates that a musical work includes a chorus section within the specified part or segment.
-
C.
hasGum
Indicates that one entity possesses or is currently chewing gum.
-
D.
hasChorus
Indicates that something (typically a song or musical piece) includes a chorus section as part of its structure.
-
E.
hasCusp
Indicates that one entity possesses or exhibits a pointed or projecting feature (a cusp) as part of its form or structure.
- F. None of above. chosen
Provenance (4 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f62b9e5ba88190a3c0d46edec7afe7 |
completed | May 2, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f627ad6d4c81909796d39d78e414f9 |
completed | May 2, 2026, 4:34 p.m. |
Created at: April 21, 2026, 5:07 p.m.