Triple
T21990089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | StAX |
E543059
|
entity |
| Predicate | parsingModel |
P41880
|
FINISHED |
| Object | pull parsing |
—
|
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: pull parsing | Statement: [StAX, parsingModel, pull parsing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parsingModel Context triple: [StAX, parsingModel, pull parsing]
-
A.
parsedBy
Indicates that one entity analyzes and interprets another entity’s structure or content, typically transforming it into a more structured or machine-readable form.
-
B.
possibleModel
chosen
Indicates that one entity can serve as a potential or candidate model or template for another entity.
-
C.
parsingComplexity
Indicates the level of difficulty or computational effort required to parse or analyze a given input or structure.
-
D.
model
Indicates that one entity serves as a representation, example, or simulation of another entity or concept.
-
E.
revisedModel
Indicates that an existing model has been updated or modified from its previous version.
- 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_69e0c48136b081908831fa907cc02e18 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1270cb67c81909a3aa2dc61c1894f |
completed | April 28, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69e6f6154e408190acc5b2c278acaff4 |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:05 p.m.