Triple
T11596026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carpenter |
E275002
|
entity |
| Predicate | originalUsageContext |
P18207
|
FINISHED |
| Object | medieval England |
—
|
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: medieval England | Statement: [Carpenter, originalUsageContext, medieval England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalUsageContext Context triple: [Carpenter, originalUsageContext, medieval England]
-
A.
originUse
Indicates that one entity is used as the original source, basis, or starting point for the creation, derivation, or use of another entity.
-
B.
originContext
chosen
Indicates the situational or environmental circumstances from which an entity, event, or piece of information originates.
-
C.
originalPrimaryUse
Indicates that something was first or chiefly intended to be used for a particular purpose or function.
-
D.
primaryConsumptionContext
Indicates the main situation, setting, or context in which something is typically used, consumed, or experienced.
-
E.
originalSiteUse
Indicates the historical or initial functional use or purpose assigned to a particular site before any subsequent changes or developments.
- 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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8946790d08190924d60bb4b523250 |
completed | April 10, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd20d188190863d1190d4c16048 |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.