Triple
T17243183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scholasticism |
E418552
|
entity |
| Predicate | methodFeature |
P41725
|
FINISHED |
| Object | question-and-answer format |
—
|
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: question-and-answer format | Statement: [Scholasticism, methodFeature, question-and-answer format]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodFeature Context triple: [Scholasticism, methodFeature, question-and-answer format]
-
A.
methodCharacteristic
chosen
Indicates that a particular method or procedure possesses a specified property, feature, or quality.
-
B.
featuresMethod
Indicates that an entity includes or provides a particular method as part of its functionality or behavior.
-
C.
method
Indicates the technique, procedure, or process used by an entity to perform an action or achieve a result.
-
D.
methodModifier
Indicates that one entity specifies a modifier (such as visibility, static, abstract, etc.) that qualifies or constrains the behavior or declaration of a method represented by another entity.
-
E.
metaFunction
Indicates that one function operates on, describes, or manipulates other functions or their behavior at a higher (meta) level.
- 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e21bb5c8190ad960f231fe54665 |
completed | April 19, 2026, 1:21 a.m. |
| PD | Predicate disambiguation | batch_69e3832553ac819091aa917c84f755b6 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.