Triple
T35638364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jersey law |
E1029782
|
entity |
| Predicate | hasHistoricalLanguageOfRecord |
P30358
|
FINISHED |
| Object | French |
—
|
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: French | Statement: [Jersey law, hasHistoricalLanguageOfRecord, French]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalLanguageOfRecord Context triple: [Jersey law, hasHistoricalLanguageOfRecord, French]
-
A.
hasMajorityLanguageHistorically
Indicates that a particular language has historically been the predominant or majority language within a given entity or region.
-
B.
historicalLanguageOfBearers
Indicates that the specified language is historically spoken or used by the bearers of a given name, title, or designation.
-
C.
historicallySpokenIn
Indicates that a language was used for spoken communication in a particular place or region during a past historical period.
-
D.
historicalLanguageStatus
Indicates that a language had a particular official, social, or functional status during a past historical period.
-
E.
languageOfHistoricalRecord
chosen
Indicates the language in which a given historical record is written or recorded.
- 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_69f76e087bdc8190a4794bf9c0bd7634 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff519b65f081909902ba83b775ef85 |
completed | May 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69ff506fccdc8190bd93269589040aed |
completed | May 9, 2026, 3:19 p.m. |
Created at: May 3, 2026, 4:05 p.m.