Triple
T21753527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fitch Tavern area |
E536973
|
entity |
| Predicate | hasPrimaryUseInPresent |
P104408
|
FINISHED |
| Object | historic interpretation |
—
|
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: historic interpretation | Statement: [Fitch Tavern area, hasPrimaryUseInPresent, historic interpretation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryUseInPresent Context triple: [Fitch Tavern area, hasPrimaryUseInPresent, historic interpretation]
-
A.
isPrimarilyUsedAs
Indicates that one entity serves mainly or most commonly in the role, function, or purpose specified by the other entity.
-
B.
hasPresentUse
Indicates that an entity is currently being used or serving a particular function at the present time.
-
C.
primaryCurrentUse
chosen
Indicates the main way something is currently being used or its principal present function.
-
D.
primaryUseOf
Indicates that one entity serves as the main or principal function, purpose, or application of another entity.
-
E.
usedPrimarilyIn
Indicates that something is mainly or most commonly employed within a particular context, domain, or purpose.
- 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_69e0c46eab808190b848242d63a17c47 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01d8c57508190b45fb974ef0ded10 |
completed | April 28, 2026, 2:38 a.m. |
| PD | Predicate disambiguation | batch_69e6969e46088190b13d6e9025775ea3 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:50 p.m.