Triple
T22105224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Punjab Cricket Association Stadium |
E546268
|
entity |
| Predicate | hasFieldEnd |
P38695
|
FINISHED |
| Object | Pavilion End |
—
|
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: Pavilion End | Statement: [Punjab Cricket Association Stadium, hasFieldEnd, Pavilion End]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFieldEnd Context triple: [Punjab Cricket Association Stadium, hasFieldEnd, Pavilion End]
-
A.
hasEnd
chosen
Indicates that one entity serves as the terminal point, boundary, or conclusion of another entity or process.
-
B.
hasFieldLength
Indicates that an entity possesses a field whose length (such as number of characters or size) is specified or constrained.
-
C.
hasFieldName
Indicates that one entity is associated with, or identified by, a specific field name in a data structure or schema.
-
D.
hasApproximateEnd
Indicates that an entity’s end point, time, or boundary is known only approximately rather than precisely.
-
E.
hasNumberOfFields
Indicates the specific count of fields or distinct data elements that an entity possesses.
- 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_69e11e378dc08190896d6a51597afd5a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12918d7a4819080283c287a253c9f |
completed | April 28, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:30 p.m.