Triple
T23155494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brian Marick |
E578424
|
entity |
| Predicate | hasConsultedFor |
P13956
|
FINISHED |
| Object | software development organizations |
—
|
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: software development organizations | Statement: [Brian Marick, hasConsultedFor, software development organizations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConsultedFor Context triple: [Brian Marick, hasConsultedFor, software development organizations]
-
A.
consulted
Indicates that one entity sought advice, information, or guidance from another entity.
-
B.
hasConsultants
Indicates that one entity engages or employs another entity to provide professional consulting services.
-
C.
hasCounsel
Indicates that one entity serves as a legal advisor or representative (counsel) for another entity.
-
D.
consultsOn
chosen
Indicates that one entity provides expert advice, guidance, or professional input to another entity regarding a specific subject, project, or decision.
-
E.
consultedWhen
Indicates that one entity is consulted at a particular time or under specific temporal conditions relative to another entity or event.
- 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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18efca1f081908ff1c34ba25f40c3 |
completed | April 29, 2026, 4:54 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:01 p.m.