Triple
T28706202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goods and Services Tax (Australia) |
E729702
|
entity |
| Predicate | isMultiStage |
P37745
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Goods and Services Tax (Australia), isMultiStage, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMultiStage Context triple: [Goods and Services Tax (Australia), isMultiStage, true]
-
A.
isMultiState
Indicates that the entity exists or operates in more than one distinct state or condition.
-
B.
hasMultiplePhases
chosen
Indicates that the related process, event, or activity occurs in more than one distinct phase or stage.
-
C.
usesMultiStepReturn
Indicates that an entity performs or supports a return process that occurs in multiple sequential steps rather than a single, direct action.
-
D.
hasStageStructure
Indicates that one entity possesses or is characterized by a particular stage-based structural organization defined by another entity.
-
E.
hasStageIn
Indicates a relationship where one entity occurs, exists, or takes place within a particular stage or phase of another process, lifecycle, or sequence.
- 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_69f043e6e9688190b6bdd6e5665498ff |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 5:45 a.m.