Triple
T34531152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFT |
E886538
|
entity |
| Predicate | followsNationalLawOf |
P131132
|
FINISHED |
| Object | Australia |
—
|
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: Australia | Statement: [NFT, followsNationalLawOf, Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsNationalLawOf Context triple: [NFT, followsNationalLawOf, Australia]
-
A.
followsLegalAuthority
Indicates that one entity acts in accordance with, or is subordinate to, the legal power, rules, or jurisdiction exercised by another entity.
-
B.
followsPolityOf
Indicates that one entity adopts, adheres to, or operates under the political system, governance model, or policy framework established by another entity.
-
C.
containsLaw
Indicates that one entity (such as a document, code, or jurisdiction) includes or encompasses a specific law within it.
-
D.
containsLawOn
Indicates that one entity (such as a document, code, or regulation) includes or sets forth legal provisions concerning another entity or subject.
-
E.
usedLegalSystemOf
chosen
Indicates that one entity applied, followed, or operated under the legal system or body of laws belonging to another entity.
- F. None of above.
Provenance (3 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_69f349cd7c148190aa99192b126d1527 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fec8aef1d8819094c7fd7074038e6b |
completed | May 9, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69fec639876481908efd84a3631a4271 |
completed | May 9, 2026, 5:29 a.m. |
Created at: May 1, 2026, 2:02 a.m.