Triple
T4398489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCAA men’s volleyball |
E99551
|
entity |
| Predicate | allowsPosition |
P52182
|
FINISHED |
| Object | libero |
—
|
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: libero | Statement: [NCAA men’s volleyball, allowsPosition, libero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsPosition Context triple: [NCAA men’s volleyball, allowsPosition, libero]
-
A.
supportsPosition
Indicates that one entity endorses, upholds, or provides backing for the stance, viewpoint, or role represented by another entity.
-
B.
allows
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
-
C.
allowedReturn
Indicates that an entity is permitted to be returned or sent back under specified conditions or rules.
-
D.
appliesToPosition
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable to a specific position or role.
-
E.
allowedOccupationOf
chosen
Indicates that one entity is permitted or authorized to hold or perform the occupation associated with 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_69b345506b408190b0e3dee616738a7d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352adce588190b9e6ed53458aa1e1 |
completed | March 12, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69b34f597998819092477efdedb51427 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:20 p.m.