Triple
T11555519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nederlander family |
E274008
|
entity |
| Predicate | generationalCount |
P52584
|
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: [Nederlander family, generationalCount, multiple generations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: generationalCount Context triple: [Nederlander family, generationalCount, multiple generations]
-
A.
generationCount
Indicates the number of times a process, entity, or version has been created, iterated, or regenerated within a sequence or lifecycle.
-
B.
hasGenerations
chosen
Indicates a relationship where an entity is associated with one or more successive generational levels or cohorts derived from it.
-
C.
currentGeneration
Indicates that an entity belongs to or is associated with the presently living or active generation within a temporal or lineage sequence.
-
D.
generationTime
Indicates the point in time at which something is created, produced, or brought into existence.
-
E.
denotesGeneration
Indicates that one entity originates, produces, or gives rise to another entity, establishing a generative or causal source-result relationship 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88a86be308190973fea5d7db8ba9d |
completed | April 10, 2026, 5:28 a.m. |
| PD | Predicate disambiguation | batch_69d85dc3fc2c8190bed7e2111301a77c |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:37 p.m.