Triple
T15375324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St George Illawarra Dragons |
E367652
|
entity |
| Predicate | enteredNRLIn |
P118504
|
FINISHED |
| Object | 1999 |
—
|
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: 1999 | Statement: [St George Illawarra Dragons, enteredNRLIn, 1999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredNRLIn Context triple: [St George Illawarra Dragons, enteredNRLIn, 1999]
-
A.
enteredARL
Indicates that an entity has gone into or gained access to an ARL (a specific location, area, or restricted zone).
-
B.
enteredStatus
Indicates that an entity has transitioned into or assumed a particular status or state.
-
C.
enteredIntoForceIn
Indicates that an agreement, law, or treaty became legally effective or operative in a specified place or jurisdiction.
-
D.
enteredIntoForce
Indicates that a law, treaty, agreement, or regulation has become legally effective and binding from a specific point in time.
-
E.
enteredIntoBy
Indicates that an agreement, contract, or formal arrangement has been initiated or established by a particular party.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e5d6f808190b0a4cdb35dc89e69 |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:18 a.m.