Triple
T36110320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Dearth |
E1044476
|
entity |
| Predicate | relationshipToLob |
P204728
|
FINISHED |
| Object | guest |
—
|
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: guest | Statement: [Mr. Dearth, relationshipToLob, guest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToLob Context triple: [Mr. Dearth, relationshipToLob, guest]
-
A.
relationshipToSinis
Indicates a familial, social, or conceptual connection that one entity has to Sinis.
-
B.
relationshipToBond
Indicates the specific type of personal, familial, or professional relationship an entity has to the person named Bond.
-
C.
relationshipToOrganization
Indicates the nature or type of connection an entity has with a specific organization, such as affiliation, membership, or role.
-
D.
relationshipToMain
Indicates that an entity has a specified type of relationship or association to a primary or main entity.
-
E.
relationshipType
Indicates the specific kind of relationship that exists between two or more entities.
- F. None of above. chosen
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_69f76e344a4c8190af3858c6d78ba88f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:08 p.m.