Triple
T18630130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle sheading |
E455390
|
entity |
| Predicate | hasTypeStatus |
P96867
|
FINISHED |
| Object | historic administrative division |
—
|
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 administrative division | Statement: [Middle sheading, hasTypeStatus, historic administrative division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeStatus Context triple: [Middle sheading, hasTypeStatus, historic administrative division]
-
A.
typeOfStatus
chosen
Indicates the specific status category or condition that an entity is classified as having.
-
B.
hasStatusBasedOn
Indicates that an entity’s status is determined or derived from another condition, event, or entity.
-
C.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
D.
hasApprovalType
Indicates that an entity is associated with a specific category or kind of approval it has received or requires.
-
E.
hasStatusIn
Indicates that an entity holds or is assigned a particular status within a specified context, scope, or system.
- 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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54f07fa8481908b2535b8fba70b7e |
completed | April 19, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:46 a.m.