Triple
T31768473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Socks |
E810870
|
entity |
| Predicate | hasPhotographAt |
P178632
|
FINISHED |
| Object | White House lawn |
—
|
NE NERFINISHED |
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: White House lawn | Statement: [Socks, hasPhotographAt, White House lawn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhotographAt Context triple: [Socks, hasPhotographAt, White House lawn]
-
A.
hasPhotographBy
Indicates that an entity is depicted in or associated with a photograph that was created or taken by a specified photographer.
-
B.
hasPhotograph
Indicates that one entity possesses, includes, or is associated with a photograph depicting or representing another entity.
-
C.
hasPhotographs
Indicates that one entity possesses, contains, or is associated with one or more photographs of another entity or subject.
-
D.
hasPhotoOn
Indicates that one entity has an associated photograph stored, displayed, or linked on another entity (such as a platform, page, or medium).
-
E.
hasPhotographedFor
Indicates that one entity has taken photographs on behalf of, or as a service for, another entity.
- 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_69f348e463e08190b902d4819195e1f0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f7117cf2188190b29e36fc1e342c60 |
completed | May 3, 2026, 9:12 a.m. |
Created at: April 30, 2026, 11:33 p.m.