Triple
T13311493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skyrian horse |
E317075
|
entity |
| Predicate | neckDescription |
P49300
|
FINISHED |
| Object | short strong neck |
—
|
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: short strong neck | Statement: [Skyrian horse, neckDescription, short strong neck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neckDescription Context triple: [Skyrian horse, neckDescription, short strong neck]
-
A.
neckCharacteristic
chosen
Indicates that an entity has a specific attribute, feature, or quality related to its neck.
-
B.
neckJoint
Indicates a joint or connection located at or functioning as the neck between two body parts or structural elements.
-
C.
neckLengthComparedTo
Indicates a comparison of the length of one entity’s neck relative to another entity’s neck.
-
D.
neckPickupType
Indicates the type or configuration of the pickup installed at the neck position of an instrument.
-
E.
headDescription
Indicates that one entity serves as a textual or semantic description of the head (primary) entity in the relationship.
- 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6babd88190a5d529df9584b9a4 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:29 p.m.