Triple
T38011470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KC |
E948374
|
entity |
| Predicate | historicallyAlternateForm |
P4181
|
FINISHED |
| Object | King's Counsel |
E501851
|
NE 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: King's Counsel | Statement: [KC, historicallyAlternateForm, King's Counsel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyAlternateForm Context triple: [KC, historicallyAlternateForm, King's Counsel]
-
A.
historicalForm
chosen
Indicates that one entity is an earlier or historically attested form or variant of another entity.
-
B.
historicallyReplaced
Indicates that one entity took the place of another in fulfilling a similar role or function at some point in history.
-
C.
historicallyFormed
Indicates that the relationship or structure arose or developed through historical processes rather than being newly created or purely theoretical.
-
D.
historicallyRecognizedAs
Indicates that an entity has been acknowledged or designated under a particular name, status, or role during a past historical period.
-
E.
historicallyDistinctFrom
Indicates that two entities are recognized as separate and not the same in historical context, despite any similarities or connections they may have.
- F. None of above.
Provenance (4 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_69f76efb4b10819092c8c2ba28ac06a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a01e4ba62748190a4756689219b6269 |
completed | May 11, 2026, 2:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4154358d4481909d6e47fbc43f0c24 |
completed | June 28, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_6a01e3fc2d908190a075c7c1549e5640 |
completed | May 11, 2026, 2:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.