Triple
T16489954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edward Frankland |
E400542
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Frankland |
E262648
|
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: Frankland | Statement: [Edward Frankland, familyName, Frankland]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Frankland Context triple: [Edward Frankland, familyName, Frankland]
-
A.
Frankland
chosen
Frankland is an English surname historically associated with the baronetcy held by Sir Thomas Frankland and his family.
-
B.
Buckland
Buckland is a settled region of the Shire in J.R.R. Tolkien’s Middle-earth, lying east of the Brandywine River and known as the homeland of the Brandybuck family.
-
C.
Buckland
Buckland is a surname most prominently associated with Jonny Buckland, the lead guitarist of the British rock band Coldplay.
-
D.
Buckland
Buckland is a small Inupiat community and city in northwestern Alaska situated along the Buckland River.
-
E.
Buckland
Buckland is a small historic community located within the Bull Run Mountains region of northern Virginia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e2f31f48190825af5934d976ab7 |
completed | April 18, 2026, 7:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00582472388190a3c338ab636da9c6 |
completed | May 10, 2026, 10:04 a.m. |
Created at: April 10, 2026, 5:13 a.m.