Triple
T32171739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Brick Breeland |
E821724
|
entity |
| Predicate | networkColleague |
P120814
|
FINISHED |
| Object | Dr. Zoe Hart |
—
|
NE NERFINISHED |
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: Dr. Zoe Hart | Statement: [Dr. Brick Breeland, networkColleague, Dr. Zoe Hart]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkColleague Context triple: [Dr. Brick Breeland, networkColleague, Dr. Zoe Hart]
-
A.
socialCircle
Indicates that one entity belongs to, or is part of, the group of people with whom another entity regularly interacts socially.
-
B.
networkOfWorkContext
Indicates a relationship where one work context is connected to or associated with other work contexts within a broader network or system.
-
C.
linkedNetwork
Indicates that two entities are connected through a shared or associated network relationship.
-
D.
hasColleagues
chosen
Indicates that one entity works alongside another in a professional or organizational context as colleagues.
-
E.
contactWith
Indicates that two entities are in direct or indirect physical or communicative interaction or touch with each other.
- 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_69f3490699a48190bbef96b198e8fade |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 12:33 a.m.