Triple
T21213447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lusitano horse |
E522775
|
entity |
| Predicate | typicalTail |
P63385
|
FINISHED |
| Object | thick and often wavy |
—
|
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: thick and often wavy | Statement: [Lusitano horse, typicalTail, thick and often wavy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTail Context triple: [Lusitano horse, typicalTail, thick and often wavy]
-
A.
tailCharacteristic
chosen
Indicates that an entity possesses a particular property, feature, or quality specifically related to its tail.
-
B.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
C.
hasTailShape
Indicates that an entity possesses a tail with a specific shape or form.
-
D.
typicalPractice
Indicates that an action, behavior, or method is commonly or customarily done in a given context or by a given group.
-
E.
typicalDynamics
Indicates the usual or characteristic way in which a system, process, or interaction evolves or behaves over time.
- 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_69e0b511ed84819099b449b4a111085c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7347088488190aa764b3f4bbac44d |
completed | April 21, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:38 p.m.