Triple
T4758480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rugby sevens |
E105644
|
entity |
| Predicate | tackleAllowed |
P58324
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [rugby sevens, tackleAllowed, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tackleAllowed Context triple: [rugby sevens, tackleAllowed, true]
-
A.
startingTackle
Indicates that an entity holds the primary (starting) role at the tackle position in a lineup or formation.
-
B.
tieAllowedAfterRegulation
Indicates that a tie outcome is permitted to occur after the application or completion of a specified regulation or regulatory process.
-
C.
offensiveTackle
Indicates that an entity plays the offensive tackle position, responsible for blocking and protecting on the offensive line in a gridiron football context.
-
D.
canBlock
Indicates that one entity has the ability or permission to prevent, obstruct, or stop the action or effect of another entity.
-
E.
allowsForeignPlayers
Indicates that an entity permits participation or involvement by players who are from foreign countries or outside its primary jurisdiction.
- F. None of above. chosen
Provenance (4 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650c11f4819098cd1f490f711dc8 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd6225c9488190afee5bb3619d0365 |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd631328fc81909b28ae0a2a3ed9bb |
completed | March 20, 2026, 3:09 p.m. |
Created at: March 20, 2026, 1:20 p.m.