Triple
T23842739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Project Method |
E591030
|
entity |
| Predicate | isAppliedIn |
P3306
|
FINISHED |
| Object | primary education |
—
|
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: primary education | Statement: [The Project Method, isAppliedIn, primary education]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAppliedIn Context triple: [The Project Method, isAppliedIn, primary education]
-
A.
appliesAt
chosen
Indicates that an action, rule, or condition is relevant to or in effect at a specific location, context, or point in time.
-
B.
appliesFrom
Indicates that a rule, condition, or effect begins to be applicable starting from a specific point in time or state.
-
C.
appliedAs
Indicates that one entity submitted itself or was put forward for consideration in a particular role, position, or context relative to another entity.
-
D.
appliesVia
Indicates that an action, rule, or effect is carried out, implemented, or achieved through a specified method, medium, or mechanism.
-
E.
appliedFrom
Indicates that an application or request was initiated starting at or originating from a particular source, location, or context.
- 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_69e25d1de32c8190a907afe9c3d6cd6d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c8898a0c8190b4d55852fc30260f |
completed | April 29, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:09 p.m.