Triple
T27636637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MatGridList |
E696488
|
entity |
| Predicate | hasChildDirective |
P42339
|
FINISHED |
| Object | mat-grid-tile |
—
|
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: mat-grid-tile | Statement: [MatGridList, hasChildDirective, mat-grid-tile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChildDirective Context triple: [MatGridList, hasChildDirective, mat-grid-tile]
-
A.
hasDirective
chosen
Indicates that one entity issues, contains, or is governed by a specific directive or instruction associated with another entity.
-
B.
hasChildIn
Indicates that one entity has a child who is located in, associated with, or present within another specified entity or context.
-
C.
has child
Indicates that one entity is the parent of another entity, which is its child.
-
D.
hasChildrenWith
Indicates that two entities share one or more biological or adopted children together.
-
E.
hasChildrenProgrammingBlock
Indicates that a programming block contains one or more subordinate (child) blocks nested within it.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 27, 2026, 2:24 p.m.