Triple
T12255121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Lebanon Emirate |
E292080
|
entity |
| Predicate | startTimeApproximation |
P48368
|
FINISHED |
| Object | early 16th century |
—
|
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: early 16th century | Statement: [Mount Lebanon Emirate, startTimeApproximation, early 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeApproximation Context triple: [Mount Lebanon Emirate, startTimeApproximation, early 16th century]
-
A.
timeStartApprox
chosen
Indicates that the associated event or state begins at an approximate, rather than exact, point in time.
-
B.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
C.
approximateAscentTime
Indicates the estimated amount of time required for an entity to ascend or climb to a specified point or elevation.
-
D.
runtimeApprox
Indicates an approximate or estimated duration of time that something (such as a process, program, or event) takes to run or complete.
-
E.
estimatedStartDate
Indicates the date on which something is expected or planned to begin, based on current information or projections.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91d38ee10819093ed41d2954bf4ef |
completed | April 10, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69d91c46dcd88190a263db30804bff36 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.