Triple
T8076200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | haystacks |
E188496
|
entity |
| Predicate | typicallyStored |
P8611
|
FINISHED |
| Object | outdoors |
—
|
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: outdoors | Statement: [haystacks, typicallyStored, outdoors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyStored Context triple: [haystacks, typicallyStored, outdoors]
-
A.
typicallySpared
Indicates that an entity is usually not affected by, excluded from, or left untouched by a particular action, process, or condition.
-
B.
store
Indicates that one entity keeps or holds another entity in a place or system for future use or access.
-
C.
storeType
Indicates the category or kind of store associated with an entity, such as its retail or service type.
-
D.
storageOption
chosen
Indicates how or where something is stored, specifying the chosen method, medium, or configuration for its storage.
-
E.
typicallyHolds
Indicates that a certain relationship or condition generally holds true in typical or normal situations, though not necessarily in all cases.
- 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_69ca82b50c708190863f661d438e68df |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb404dc7ac8190956b5c2f5aeac6b2 |
completed | March 31, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69cb049f1614819087360d1a4c6f0faa |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:28 p.m.