Triple
T26883610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gray Matter Technologies |
E676980
|
entity |
| Predicate | hasCurrentKeyFigure |
P810
|
FINISHED |
| Object | Elliott Schwartz |
E1755335
|
NE 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: Elliott Schwartz | Statement: [Gray Matter Technologies, hasCurrentKeyFigure, Elliott Schwartz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCurrentKeyFigure Context triple: [Gray Matter Technologies, hasCurrentKeyFigure, Elliott Schwartz]
-
A.
hasKeyFigure
chosen
Indicates that an entity includes, involves, or is characterized by an important or central person relevant to it.
-
B.
hasKeyMeasure
Indicates that one entity is the primary or defining metric, indicator, or quantitative measure used to assess or evaluate another entity.
-
C.
keyFigureDuring
Indicates that an entity played a central or highly influential role during a specified period, event, or process.
-
D.
hasKeyResult
Indicates that an entity is associated with a specific key result it aims to achieve or is responsible for.
-
E.
hasCurrent
Indicates that an entity presently possesses, exhibits, or is associated with a particular state, attribute, or resource at the current time.
- F. None of above.
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_69eee9bc0c90819085608c8bdc513a57 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1247e34bd4819084ef6268df58ad85 |
completed | May 24, 2026, 12:35 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 27, 2026, 5:40 a.m.