Triple
T35486576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dolmen Pierre de la Fée |
E1025612
|
entity |
| Predicate | approximateUsePeriod |
P60853
|
FINISHED |
| Object | late Neolithic |
—
|
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: late Neolithic | Statement: [Dolmen Pierre de la Fée, approximateUsePeriod, late Neolithic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateUsePeriod Context triple: [Dolmen Pierre de la Fée, approximateUsePeriod, late Neolithic]
-
A.
activePeriodApproximate
Indicates that the time span during which an entity was active is known only approximately rather than as precise dates.
-
B.
timePeriodApproximation
Indicates that the associated time period is an estimate or approximation rather than an exact, precise value.
-
C.
approximateIntroductionPeriod
chosen
Indicates the approximate time period during which an entity was first introduced or came into use.
-
D.
laterUsePeriod
Indicates that one entity is used or becomes relevant after a specified later time period relative to another.
-
E.
hasApproximateUse
Indicates that one entity is used for a purpose that is similar to, but not exactly the same as, the use or function of another 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_69f76dfbcdd881908c7b0b6bc502252b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff5f5ecc808190b2df364da108ff4c |
completed | May 9, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69ff5b84131c8190bf81d7fb53e934bc |
completed | May 9, 2026, 4:06 p.m. |
Created at: May 3, 2026, 4:04 p.m.