Triple
T16551995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zealandia |
E402093
|
entity |
| Predicate | recognitionDebate |
P57644
|
FINISHED |
| Object | status as a distinct continent is debated |
—
|
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: status as a distinct continent is debated | Statement: [Zealandia, recognitionDebate, status as a distinct continent is debated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognitionDebate Context triple: [Zealandia, recognitionDebate, status as a distinct continent is debated]
-
A.
canDebate
Indicates that one entity has the ability or permission to engage in a debate or argumentative discussion with another entity.
-
B.
fieldOfDebate
chosen
Indicates that something is the subject or domain around which a debate or argumentative discussion is centered.
-
C.
majorDebateWith
Indicates a significant, often public or formal, debate or dispute occurring between two entities.
-
D.
canSpeakInDebates
Indicates that an entity has the ability or permission to speak during formal debates.
-
E.
keyFigureInDebate
Indicates that an entity plays a central, influential, or prominently recognized role in a particular debate or controversy.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34fc56f9081908bb8f6433a1a688d |
completed | April 18, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:15 a.m.