Triple
T38612750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLE |
E934523
|
entity |
| Predicate | typicalSpeakersAgeGroup |
P200700
|
FINISHED |
| Object | adolescents and young adults |
—
|
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: adolescents and young adults | Statement: [MLE, typicalSpeakersAgeGroup, adolescents and young adults]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSpeakersAgeGroup Context triple: [MLE, typicalSpeakersAgeGroup, adolescents and young adults]
-
A.
primarySpeakersAgeGroup
Indicates the age range category to which the main or primary speakers in a context belong.
-
B.
typicalSpeakersAre
chosen
Indicates that the entities specified are the kinds of speakers who typically use or produce the expression or language in question.
-
C.
typicalAudience
Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
-
D.
ageGroup
Indicates the categorical age range or bracket to which an entity belongs.
-
E.
youngerSpeakers
Indicates that the related speakers are younger in age relative to some other referenced group or individual.
- 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_69f76eccd6d081909ccce171011739a1 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.