Triple
T6892065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basque pelota |
E159070
|
entity |
| Predicate | typicalWallConfiguration |
P67991
|
FINISHED |
| Object | one-wall court |
—
|
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: one-wall court | Statement: [Basque pelota, typicalWallConfiguration, one-wall court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalWallConfiguration Context triple: [Basque pelota, typicalWallConfiguration, one-wall court]
-
A.
typicalUnitConfiguration
chosen
Indicates the standard or commonly used arrangement, composition, or setup of a unit in a given context.
-
B.
hasWallShape
Indicates that an entity possesses a wall whose form or outline matches a specified geometric or structural shape.
-
C.
hasWallType
Indicates the specific kind or classification of wall associated with an entity.
-
D.
wallFeature
Indicates that one entity functions as a structural or design feature associated with a wall of another entity.
-
E.
wallMaterial
Indicates that one entity is the material from which a wall or walls of another entity are constructed.
- 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_69c6883568c8819081db6407e892cccc |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d92ecbdc8190992f9c7f4f33f4c4 |
completed | March 27, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b53e9881909ec298daa9f1913b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:24 p.m.