Triple
T6450246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L’Anse aux Meadows National Historic Site |
E139844
|
entity |
| Predicate | periodOfOccupationStart |
P10338
|
FINISHED |
| Object | c. 1000 |
—
|
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: c. 1000 | Statement: [L’Anse aux Meadows National Historic Site, periodOfOccupationStart, c. 1000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodOfOccupationStart Context triple: [L’Anse aux Meadows National Historic Site, periodOfOccupationStart, c. 1000]
-
A.
officeHolderStartTime
Indicates the date and time at which an individual begins holding a particular office or position.
-
B.
occupiesSince
Indicates that an entity has continuously occupied or held a position, place, or role starting from a specified point in time.
-
C.
timeInOfficeBeginsIn
Indicates the point in time or date when an entity’s term, tenure, or period in office starts.
-
D.
lastOfficeHolderStartDate
Indicates the date on which the most recent person to hold a particular office or position began their term.
-
E.
beganInYear
chosen
Indicates that an event, process, or state started in a specific calendar year.
- 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_69c008b301948190a35854e5284dc822 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c069b2c7bc81908c683ec22cad9628 |
completed | March 22, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69c0673b44148190aed70084f0ff4992 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:47 p.m.