Triple
T6414529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Count |
E127790
|
entity |
| Predicate | historicallyGoverned |
P44467
|
FINISHED |
| Object | county |
—
|
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: county | Statement: [Count, historicallyGoverned, county]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyGoverned Context triple: [Count, historicallyGoverned, county]
-
A.
historicalRegionGoverned
chosen
Indicates that a subject entity exercised governing authority over a particular historical region during a specified period.
-
B.
laterGovernedAs
Indicates that an entity subsequently held governing authority over another entity at a later time.
-
C.
hasHistoricalPolity
Indicates a relationship where an entity is associated with a political unit or state that existed in the past.
-
D.
hasHistoricalGovernmentForm
Indicates that an entity has, at some point in the past, been governed under a particular form or system of government.
-
E.
historicallyPartOf
Indicates that one entity was formerly a component, region, or subdivision of another entity during a past historical period, but is not necessarily part of it in the present.
- 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_69c0083815208190a9b299b8e0640218 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c068e6bd3881909b1979de5cdf17fb |
completed | March 22, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69c060f5d4e481909d1366190607b586 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:42 p.m.