Triple
T30090188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Melbourne Football Club |
E764707
|
entity |
| Predicate | originalCode |
P201682
|
FINISHED |
| Object | Victorian Football Association |
—
|
NE NERFINISHED |
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: Victorian Football Association | Statement: [North Melbourne Football Club, originalCode, Victorian Football Association]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalCode Context triple: [North Melbourne Football Club, originalCode, Victorian Football Association]
-
A.
fullCode
Indicates that an entity is represented by a complete, fully specified code rather than a partial or abbreviated one.
-
B.
originalFunction
Indicates that one entity serves as the initial or primary function from which another function or behavior is derived or defined.
-
C.
scriptCode
Indicates that an entity is associated with a particular writing system or script, identified by a standardized script code.
-
D.
codeOn
Indicates that one entity writes, develops, or modifies software using or for another entity (such as a platform, project, or codebase).
-
E.
originProgram
Indicates the program, initiative, or source project from which an entity, item, or record originally comes.
- 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00144238708190acbec3f791cc873e |
completed | May 10, 2026, 5:14 a.m. |
| PD | Predicate disambiguation | batch_6a00120244a4819090ef39070aba9d99 |
completed | May 10, 2026, 5:05 a.m. |
| PDg | Predicate description generation | batch_6a001440a26c81908ba50779bb6e1679 |
completed | May 10, 2026, 5:14 a.m. |
Created at: April 29, 2026, 7:05 p.m.