Triple
T3337296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huguenot Street Historic District |
E70167
|
entity |
| Predicate | languageOfHistoricalCommunity |
P1434
|
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: [Huguenot Street Historic District, languageOfHistoricalCommunity, French]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfHistoricalCommunity Context triple: [Huguenot Street Historic District, languageOfHistoricalCommunity, French]
-
A.
languageOfHistoricalRecord
Indicates the language in which a given historical record is written or recorded.
-
B.
historicallySpokenIn
chosen
Indicates that a language was used for spoken communication in a particular place or region during a past historical period.
-
C.
historicalLanguageGroup
Indicates that two or more entities belong to the same historically defined language group or family, based on shared linguistic ancestry or development.
-
D.
heritageLanguage
Indicates that one entity is the ancestral or culturally inherited language associated with another entity.
-
E.
languageOfFounders
Indicates the language or languages spoken or used by the founders of an entity.
- 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_69ad85a24f208190bcf83131bfed3521 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb1bc31b4819085f01e0b5a7cbc5d |
completed | March 8, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69ada42c2ba8819091136805ce17b39d |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.