Triple
T16832010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clayborn Temple |
E409172
|
entity |
| Predicate | functionDuring1960s |
P41834
|
FINISHED |
| Object | meeting place for civil rights leaders |
—
|
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: meeting place for civil rights leaders | Statement: [Clayborn Temple, functionDuring1960s, meeting place for civil rights leaders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionDuring1960s Context triple: [Clayborn Temple, functionDuring1960s, meeting place for civil rights leaders]
-
A.
functionDuring20thCentury
Indicates that the function, role, or operation of one entity with respect to another occurred at some time during the 20th century.
-
B.
screenDebutDecade
Indicates the decade during which an entity first appeared on screen (e.g., in film or television).
-
C.
testFifties
Indicates that an entity is associated with, belongs to, or is being evaluated in the context of the 1950s time period.
-
D.
developmentStartDecade
Indicates the decade during which the development or creation of an entity was initiated.
-
E.
operatedInDecade
chosen
Indicates that an entity carried out its operations or activities during a specified decade.
- 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b317af8c8190a09cb6d60d28e342 |
completed | April 18, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.