Triple
T147514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Young Republicans |
E3362
|
entity |
| Predicate | typicalAgeRange |
P2736
|
FINISHED |
| Object | 18–40 |
—
|
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: 18–40 | Statement: [Young Republicans, typicalAgeRange, 18–40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAgeRange Context triple: [Young Republicans, typicalAgeRange, 18–40]
-
A.
ageRange
chosen
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
B.
servesAgeRange
Indicates that a service, product, or offering is intended for or applicable to entities within a specified age range.
-
C.
typicalEnergyRange
Indicates the usual or characteristic range of energy values associated with an entity, process, or interaction.
-
D.
typicalMembers
Indicates that the related entities are representative or characteristic members of a larger group, category, or class.
-
E.
hasAge
Indicates that an entity possesses a specific age value, typically expressed as a number of time units since its birth or creation.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a258808ff08190a06b6206f635612b |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a256580c2c8190beecca60ca8595f3 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.