Triple
T26047708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mesoamerican ballgame |
E647878
|
entity |
| Predicate | forbidsUseOf |
P272
|
FINISHED |
| Object | feet |
—
|
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: feet | Statement: [Mesoamerican ballgame, forbidsUseOf, feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forbidsUseOf Context triple: [Mesoamerican ballgame, forbidsUseOf, feet]
-
A.
restrictedFromUseFor
Indicates that something is prohibited or limited from being used for a specified purpose, context, or application.
-
B.
prohibits
chosen
Indicates that one entity forbids or disallows another entity from performing a specific action or being in a certain state.
-
C.
isProhibitedFor
Indicates that a certain action, object, or condition is not allowed or is forbidden for a specified entity or group.
-
D.
shouldNotBeUsedWith
Indicates that one entity is not recommended or is prohibited from being used in combination with another entity.
-
E.
shouldNotBeUsedIn
Indicates that one entity is not appropriate, allowed, or recommended for use within the context, scope, or situation defined by another entity.
- 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_69e77e8d419481908004e6318d28aaab |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6065b4a248190a3fd8e9aee46d773 |
completed | May 2, 2026, 2:12 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 22, 2026, 9:10 a.m.