Triple
T5093844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Husky |
E114818
|
entity |
| Predicate | originUse |
P60698
|
FINISHED |
| Object | pulling loads over long distances |
—
|
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: pulling loads over long distances | Statement: [Husky, originUse, pulling loads over long distances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originUse Context triple: [Husky, originUse, pulling loads over long distances]
-
A.
originalFor
Indicates that one entity serves as the source, basis, or prototype from which another entity is derived, adapted, or created.
-
B.
originallyBy
Indicates that one entity is the original creator, author, or source of another entity.
-
C.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
-
D.
originallyIn
Indicates that something first appeared, was created, or was initially located within a particular context, source, or place.
-
E.
originNote
Indicates a note or comment that explains the origin, source, or provenance of an entity or relationship.
- 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_69bd443fc49c819089629c00e311310c |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75454920819086e09d6055087e40 |
completed | March 20, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69bd715c0a448190afc837c6c31dc6ab |
completed | March 20, 2026, 4:10 p.m. |
| PDg | Predicate description generation | batch_69bd72b8d7a88190ad53fae64f17e22c |
completed | March 20, 2026, 4:15 p.m. |
Created at: March 20, 2026, 1:40 p.m.