Triple
T12463160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verzy |
E297849
|
entity |
| Predicate | FauxDeVerzyStatus |
P103705
|
FINISHED |
| Object | protected natural site |
—
|
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: protected natural site | Statement: [Verzy, FauxDeVerzyStatus, protected natural site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FauxDeVerzyStatus Context triple: [Verzy, FauxDeVerzyStatus, protected natural site]
-
A.
deFactoStatus
Indicates that one entity holds a role, position, or status in practice or by custom, even if it is not formally or legally recognized.
-
B.
falseFor
Indicates that a given statement or proposition does not hold true or is invalid specifically in the context of the referenced entity or situation.
-
C.
verificationStatus
Indicates whether an entity, claim, or item has been checked and confirmed as authentic, accurate, or compliant according to a defined verification process.
-
D.
notStatus
chosen
Indicates that an entity does not have, is not in, or does not match a specified status or state.
-
E.
realityStatus
Indicates the relationship between an entity and its state of existence or authenticity within a given context or world (e.g., real, fictional, hypothetical, simulated).
- 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_69d6ada270808190b1a2b2e7b02bb426 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e626dbc8190ac7dcdb542ba9b0c |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d3f701c81909dd0e00251ac8553 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:56 p.m.