Triple
T37159836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bertram Cooper |
E920616
|
entity |
| Predicate | officeRule |
P195127
|
FINISHED |
| Object | no shoes in his office |
—
|
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: no shoes in his office | Statement: [Bertram Cooper, officeRule, no shoes in his office]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeRule Context triple: [Bertram Cooper, officeRule, no shoes in his office]
-
A.
officeBefore
Indicates that one office, position, or term is held or occurs earlier in time than another office, position, or term.
-
B.
officeAction
Indicates an official act or decision taken by an office or authority in response to a matter, request, or proceeding.
-
C.
officeWon
Indicates that a candidate successfully secured an elected office or position as the result of an election or selection process.
-
D.
officeElement
chosen
Indicates that one entity is a component, feature, or item that forms part of an office or office environment in relation to another entity.
-
E.
defaultOfficeSuite
Indicates that a particular office software suite is set as the primary or standard choice to be used by default.
- 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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a0048697bd081909073640666ca6a96 |
completed | May 10, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_6a0047bf3c248190a9ac97a7afdfe2cb |
completed | May 10, 2026, 8:54 a.m. |
Created at: May 3, 2026, 4:15 p.m.