Triple
T231502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Statuary Hall |
E4419
|
entity |
| Predicate | publicFunction |
P9533
|
FINISHED |
| Object | civic education about U.S. history |
—
|
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: civic education about U.S. history | Statement: [Statuary Hall, publicFunction, civic education about U.S. history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicFunction Context triple: [Statuary Hall, publicFunction, civic education about U.S. history]
-
A.
formerFunction
Indicates that an entity previously held a specific role, position, or function but no longer does so.
-
B.
originalFunction
Indicates that one entity serves as the initial or primary function from which another function or behavior is derived or defined.
-
C.
notFunction
Indicates that the specified entity does not serve as a function or is not used in a functional role within the given context.
-
D.
currentFunction
Indicates that an entity is presently serving in a specific role, position, or capacity.
-
E.
assignedFunction
Indicates that a specific role, duty, or function has been formally allocated to an 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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25e0868708190ad551ca06cc57f4a |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b5a075081909b0e9b88c1492d5a |
completed | Feb. 28, 2026, 3:04 a.m. |
| PDg | Predicate description generation | batch_69a25e06dd7c8190a8cbb76cee3c6e4b |
completed | Feb. 28, 2026, 3:16 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.