Triple
T617711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enlightenment science |
E14442
|
entity |
| Predicate | hasEndApproximate |
P8204
|
FINISHED |
| Object | early 19th 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 19th century | Statement: [Enlightenment science, hasEndApproximate, early 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEndApproximate Context triple: [Enlightenment science, hasEndApproximate, early 19th century]
-
A.
hasApproximateEnd
chosen
Indicates that an entity’s end point, time, or boundary is known only approximately rather than precisely.
-
B.
hasApproximateDuration
Indicates that one entity has a duration that is estimated or not exact, typically expressed as an approximate length of time.
-
C.
hasPageCountApprox
Indicates that an entity is associated with an approximate or estimated number of pages, rather than an exact page count.
-
D.
hasApproximateValue
Indicates that one entity’s value is close to, but not exactly equal to, the value of another entity within an acceptable margin of error.
-
E.
hasApproximateDepth
Indicates that an entity is associated with a depth value that is not exact but estimated or approximate.
- 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e2418c881908552d2c4a5006e97 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfd15288190b4abdbd0bce3edcd |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.