Triple
T19838690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martim Moniz (former parish) |
E476663
|
entity |
| Predicate | squareUsedFor |
P67620
|
FINISHED |
| Object | public events |
—
|
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: public events | Statement: [Martim Moniz (former parish), squareUsedFor, public events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: squareUsedFor Context triple: [Martim Moniz (former parish), squareUsedFor, public events]
-
A.
squareUse
Indicates that one entity uses or occupies another entity in a square or rectangular configuration, typically implying a grid-like or evenly spaced arrangement.
-
B.
squareGivenBy
Indicates that one entity is a square (or square-shaped region) that has been specified, defined, or provided by another entity.
-
C.
arenaUsed
chosen
Indicates that a particular arena or venue is utilized or has been employed for a specific event, activity, or purpose.
-
D.
squareProperty
Indicates that one entity is the square (second power) of a numerical property or value associated with another entity.
-
E.
squareName
Indicates that an entity is identified by or associated with the name of a square (such as a public square or plaza).
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65803bb988190a4e7c0035058feba |
completed | April 20, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e5305bda388190a23b7191768107b1 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.