Triple
T25652121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monteux family |
E643128
|
entity |
| Predicate | generationalSpan |
P77133
|
FINISHED |
| Object | multiple generations |
—
|
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: multiple generations | Statement: [Monteux family, generationalSpan, multiple generations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: generationalSpan Context triple: [Monteux family, generationalSpan, multiple generations]
-
A.
lifetimeInGenerations
chosen
Indicates the number of successive generations over which something (e.g., an effect, trait, or validity) persists or remains applicable.
-
B.
hasGenerations
Indicates a relationship where an entity is associated with one or more successive generational levels or cohorts derived from it.
-
C.
lifespan
Indicates the duration of time between an entity’s birth (or creation) and its death (or end).
-
D.
designatesGenerationOf
Indicates that one entity formally assigns or specifies another entity as the generation or creation of something (e.g., a document, product, or version).
-
E.
generationTime
Indicates the point in time at which something is created, produced, or brought into existence.
- 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_69e77e7d8a848190a98d0162325fd780 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5faa88aec819082bca8efba424a91 |
completed | May 2, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 6:26 p.m.