Triple
T10253542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argentina national rugby union team |
E240403
|
entity |
| Predicate | testMatchStatus |
P93208
|
FINISHED |
| Object | Tier 1 nation |
—
|
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: Tier 1 nation | Statement: [Argentina national rugby union team, testMatchStatus, Tier 1 nation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testMatchStatus Context triple: [Argentina national rugby union team, testMatchStatus, Tier 1 nation]
-
A.
testStatus
Indicates the current outcome or state of a test, such as whether it has passed, failed, or is still in progress.
-
B.
TestStatus
Indicates the current outcome or state of a test, such as whether it has passed, failed, is in progress, or has not yet been executed.
-
C.
statusMatchWith
Indicates that two entities share the same status or that one entity’s status corresponds to another according to a defined matching rule.
-
D.
statusMatchAvailable
Indicates that the current status of an entity matches a condition or value that qualifies it as available.
-
E.
matchOf
Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
- 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d328272c8190a3548d7f7f38cfc4 |
completed | April 7, 2026, 9:49 a.m. |
| PD | Predicate disambiguation | batch_69d4d1ebd6c88190a1f3f4a72a99d6fe |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d32741888190928b045e2241cfac |
completed | April 7, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:29 a.m.