Triple
T8724005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brooks Hatlen |
E207083
|
entity |
| Predicate | famousLineContext |
P77440
|
FINISHED |
| Object | "Brooks was here" inscription |
—
|
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: "Brooks was here" inscription | Statement: [Brooks Hatlen, famousLineContext, "Brooks was here" inscription]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousLineContext Context triple: [Brooks Hatlen, famousLineContext, "Brooks was here" inscription]
-
A.
dialogueLine
chosen
Indicates that one entity is a specific spoken or written line of dialogue expressed by another entity (such as a character or speaker).
-
B.
famousCall
Indicates that one entity makes a phone call to another entity who is widely known or celebrated.
-
C.
associatedWithFamousSlogan
Indicates that an entity is connected to, known for, or commonly linked with a particular famous slogan.
-
D.
famousCallBy
Indicates that one entity is famously referred to or called by a particular name or title by another entity or source.
-
E.
characterCatchphrase
Indicates that a particular phrase is commonly and distinctively used by a character as their catchphrase.
- 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_69ca835811d8819081ea00fd2a2c9a1c |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d0791208190b043332247372d7b |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457093188190959287a6458651c6 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:36 p.m.