Triple
T34010663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Betty Bold |
E872100
|
entity |
| Predicate | maintainsCoverAs |
P188459
|
FINISHED |
| Object | human suburban resident |
—
|
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: human suburban resident | Statement: [Betty Bold, maintainsCoverAs, human suburban resident]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintainsCoverAs Context triple: [Betty Bold, maintainsCoverAs, human suburban resident]
-
A.
coverStatus
Indicates the current state or condition of coverage that applies to an entity, such as whether coverage is active, pending, expired, or otherwise classified.
-
B.
isCover
Indicates that one entity functions as a protective or concealing layer over another entity.
-
C.
coverUpBy
Indicates that one entity conceals, suppresses, or hides the actions, information, or wrongdoing associated with another entity.
-
D.
isCoveredIn
Indicates that one entity has its surface or area overlaid, coated, or blanketed by another substance or material.
-
E.
coverPosition
Indicates that one entity occupies or shields a specific position or area, providing coverage for it.
- 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_69f349a08848819084b348d64c1879c3 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba789c1188190973a919bfe2871f3 |
completed | May 6, 2026, 8:41 p.m. |
Created at: May 1, 2026, 1:51 a.m.