Triple
T17118872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Konik horse |
E415410
|
entity |
| Predicate | hasBuild |
P126011
|
FINISHED |
| Object | stocky |
—
|
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: stocky | Statement: [Konik horse, hasBuild, stocky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuild Context triple: [Konik horse, hasBuild, stocky]
-
A.
hasBuildsFor
Indicates that one entity creates, compiles, or prepares builds specifically intended to run on or support another entity (such as a target platform, environment, or configuration).
-
B.
hasBuilt
Indicates that one entity is the creator or constructor of another entity.
-
C.
hasBuildingFrom
Indicates a relationship where a location or site possesses or includes a building that originates from, or was constructed in, a specified time period, source, or context.
-
D.
hasBuildingStatus
Indicates the current condition, classification, or operational state assigned to a building.
-
E.
hasConstruction
Indicates that one entity possesses, contains, or is characterized by a particular construction, structure, or built form associated with it.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3e8086a388190a655a044feccab14 |
completed | April 18, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69e35d6b1b988190a8d6b6fe78c35e59 |
completed | April 18, 2026, 10:31 a.m. |
| PDg | Predicate description generation | batch_69e37542d060819082aa73948eb8ebd4 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:35 a.m.