Triple
T17872025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henkin construction |
E446858
|
entity |
| Predicate | methodStep |
P100318
|
FINISHED |
| Object | extend the language with new constant symbols |
—
|
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: extend the language with new constant symbols | Statement: [Henkin construction, methodStep, extend the language with new constant symbols]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodStep Context triple: [Henkin construction, methodStep, extend the language with new constant symbols]
-
A.
stepInRoutine
chosen
Indicates that an action or event occurs as an ordered step within a larger, structured routine or sequence of activities.
-
B.
method
Indicates the technique, procedure, or process used by an entity to perform an action or achieve a result.
-
C.
stepTakes
Indicates that one step directly follows or is taken after another step in a process or sequence.
-
D.
stepType
Indicates the specific kind or category of step an entity represents within a process or sequence.
-
E.
typicalStep
Indicates that an action, event, or sub-process is a standard or commonly occurring step within a larger process or procedure.
- 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_69d8b9f4c22c819093c2680434472894 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49aa30ff8819090c51c1d7767e952 |
completed | April 19, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e6d2e88190ad9ef9f8a99f13e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:18 a.m.