Triple
T25460308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Lawn of the White House |
E638026
|
entity |
| Predicate | hasSecondaryUseTime |
P135328
|
FINISHED |
| Object | evening events |
—
|
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: evening events | Statement: [North Lawn of the White House, hasSecondaryUseTime, evening events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryUseTime Context triple: [North Lawn of the White House, hasSecondaryUseTime, evening events]
-
A.
hasSecondaryUsage
Indicates that an entity is associated with an additional, non-primary function or purpose beyond its main intended use.
-
B.
hasTypicalUseTime
Indicates the usual or expected duration or time period during which something is commonly used or in operation.
-
C.
hasSecondary
Indicates that an entity is associated with an additional or subordinate counterpart beyond its primary one.
-
D.
hasSecondaryPeriod
chosen
Indicates that an entity is associated with an additional, subordinate, or second time period beyond its primary period.
-
E.
hasSecondarySpace
Indicates that an entity possesses or is associated with an additional, subordinate, or auxiliary space beyond its primary one.
- 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 21, 2026, 2:11 p.m.