Triple
T34639324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guam national rugby union team |
E889512
|
entity |
| Predicate | fullSide |
P179550
|
FINISHED |
| Object | 15 players on field |
—
|
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: 15 players on field | Statement: [Guam national rugby union team, fullSide, 15 players on field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullSide Context triple: [Guam national rugby union team, fullSide, 15 players on field]
-
A.
fullLine
Indicates that one entity represents a complete, uninterrupted line rather than a partial or segmented portion.
-
B.
singleSideOf
Indicates that one entity constitutes a single side or face of another entity, typically within a larger multi-sided structure or object.
-
C.
singleSide
Indicates that the relationship or action involves only one side or participant, without a corresponding or reciprocal counterpart.
-
D.
originalSide
Indicates that an entity remains on or is associated with its initial or starting side in a given context or relationship.
-
E.
onSide
Indicates that one entity is positioned along or adjacent to the side of another entity.
- 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_69f349d724848190b63ad3407e0006d9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f722c1bc648190a79bfdc722dcaaa4 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: May 1, 2026, 2:04 a.m.