Triple
T22404375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guernsey |
E553843
|
entity |
| Predicate | retainedFromNormandy |
P148028
|
FINISHED |
| Object | legal traditions |
—
|
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: legal traditions | Statement: [Guernsey, retainedFromNormandy, legal traditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retainedFromNormandy Context triple: [Guernsey, retainedFromNormandy, legal traditions]
-
A.
retainsMemoriesOf
Indicates that one entity continues to hold or preserve memories about another entity or about events involving that entity.
-
B.
retained
Indicates that one entity keeps possession, control, or continued engagement of another entity over a period of time.
-
C.
remnantName
Indicates that an entity is identified by a name specifically associated with a remaining part, leftover, or surviving fragment of something previously whole.
-
D.
remnants
Indicates that parts or traces of something remain after the main portion has been removed, used, or destroyed.
-
E.
returnedFromRetirement
Indicates that an entity has resumed an activity, role, or position after having previously retired from it.
- F. None of above. chosen
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_69e11e4da7048190b4387d422a9a0de5 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f158b6762c8190991fc14c5ca8e609 |
completed | April 29, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69e8aa39e3388190b659d59948ebf3e6 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:46 p.m.