Triple
T34222490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wonderful Barn |
E877959
|
entity |
| Predicate | functionDuringConstruction |
P44843
|
FINISHED |
| Object | employment for local poor |
—
|
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: employment for local poor | Statement: [Wonderful Barn, functionDuringConstruction, employment for local poor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionDuringConstruction Context triple: [Wonderful Barn, functionDuringConstruction, employment for local poor]
-
A.
operatorDuringConstruction
Indicates that an entity serves as the operator of another entity specifically during its construction phase.
-
B.
flagDuringConstruction
Indicates that an entity is marked or flagged specifically for the duration of its construction or creation process.
-
C.
constructedDuring
Indicates that one entity was built or created within the time period defined by another entity or event.
-
D.
functionDuringEvent
Indicates that a particular function, role, or operation is active or carried out during a specified event.
-
E.
buildingFunctionDuring
chosen
Indicates the role or purpose a building serves during a specified time period or interval.
- 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_69f349b16d0481908754e3069f05e0c1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: May 1, 2026, 1:55 a.m.