Triple
T12945340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ellicott Square Company |
E309746
|
entity |
| Predicate | roleInConstruction |
P6124
|
FINISHED |
| Object | financing of Ellicott Square Building |
—
|
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: financing of Ellicott Square Building | Statement: [Ellicott Square Company, roleInConstruction, financing of Ellicott Square Building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInConstruction Context triple: [Ellicott Square Company, roleInConstruction, financing of Ellicott Square Building]
-
A.
plannedRole
Indicates that an entity is expected or intended to assume a particular role or function in a planned or future context.
-
B.
roleInvolves
chosen
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
C.
roleInEngine
Indicates the specific function or responsibility an entity has within an engine or engine-like system.
-
D.
roleInUp
Indicates that an entity holds or plays a specific role in a higher-level or encompassing entity or context.
-
E.
roleInInitiation
Indicates the specific part or function an entity plays in starting or triggering an event, process, or interaction.
- 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_69d7bdfb57a88190836b743e2825feca |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97db69f548190a1a693bc0d6c191a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:43 p.m.