Triple
T85529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Civilian Conservation Corps |
E1721
|
entity |
| Predicate | appliesToAgeGroup |
P3005
|
FINISHED |
| Object | young men |
—
|
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: young men | Statement: [Civilian Conservation Corps, appliesToAgeGroup, young men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToAgeGroup Context triple: [Civilian Conservation Corps, appliesToAgeGroup, young men]
-
A.
ageRange
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
B.
servesAgeRange
chosen
Indicates that a service, product, or offering is intended for or applicable to entities within a specified age range.
-
C.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
D.
hasAge
Indicates that an entity possesses a specific age value, typically expressed as a number of time units since its birth or creation.
-
E.
eligibilityCriteria
Indicates the conditions or requirements that must be satisfied for an entity to qualify for or be considered eligible for something.
- 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_69a24c8150408190910a693eb51c1f71 |
completed | Feb. 28, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69a250e401288190ba12322c9c5f07c9 |
completed | Feb. 28, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69a24eb59e808190811c20518f39b1cc |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.