Triple
T23301573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | residual maker matrix |
E590316
|
entity |
| Predicate | trace |
P151781
|
FINISHED |
| Object | n - p (for full column rank X) |
—
|
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: n - p (for full column rank X) | Statement: [residual maker matrix, trace, n - p (for full column rank X)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trace Context triple: [residual maker matrix, trace, n - p (for full column rank X)]
-
A.
track
Indicates that one entity follows, monitors, or keeps a record of another entity’s state, behavior, or progress over time.
-
B.
traceOf
Indicates that one entity is a remaining sign, mark, or residual evidence of the presence, existence, or action of another entity.
-
C.
trap
Indicates that an entity captures, confines, or ensnares another entity, typically preventing its escape or movement.
-
D.
traceProperty
Indicates that a property or attribute of an entity is being tracked, recorded, or monitored over time or through a process.
-
E.
trigger
Indicates that one entity causes or initiates an event, state, or action in another entity or system.
- F. None of above. chosen
Provenance (4 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_69e25d1c0ecc8190a355aa229f06d0e0 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196d37fd08190ad2d199c54324c02 |
completed | April 29, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d88b4ec8190a2a17a88e0eda178 |
completed | April 28, 2026, 2:38 a.m. |
Created at: April 17, 2026, 5:04 p.m.