Triple
T5262259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neolithic Flint Mines at Spiennes |
E118852
|
entity |
| Predicate | earliestActivity |
P4785
|
FINISHED |
| Object | mid-5th millennium BC |
—
|
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: mid-5th millennium BC | Statement: [Neolithic Flint Mines at Spiennes, earliestActivity, mid-5th millennium BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestActivity Context triple: [Neolithic Flint Mines at Spiennes, earliestActivity, mid-5th millennium BC]
-
A.
earlyActivity
Indicates that an entity begins or performs a specified activity earlier than a usual, expected, or referenced time.
-
B.
precursorActivity
Indicates that one activity occurs earlier and contributes causally or preparatorily to the initiation of another activity.
-
C.
startsAt
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
-
D.
activityStartApprox
chosen
Indicates that the start time of an activity is known only approximately, rather than as an exact timestamp.
-
E.
laterActivity
Indicates that one activity occurs after another in time, establishing a temporal ordering between them.
- 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_69bd446a42c88190b7ecbef006561d55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7bd0c5f48190a1be89314c59f96b |
completed | March 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69bd77c55224819096c0bcfcfae79bd3 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:50 p.m.