Triple
T33448292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pedra do Sino trail |
E856563
|
entity |
| Predicate | isWellMarked |
P2130
|
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: [Pedra do Sino trail, isWellMarked, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWellMarked Context triple: [Pedra do Sino trail, isWellMarked, true]
-
A.
isMarkedAccordingTo
Indicates that one entity bears marks, labels, or annotations that conform to the rules, standards, or criteria specified by another entity or reference.
-
B.
hasMarker
chosen
Indicates that one entity possesses, is associated with, or is identified by a specific marker.
-
C.
wasMarkedBy
Indicates that an entity bears a mark, sign, or indication that was applied or caused by another entity.
-
D.
hasProofMark
Indicates that an entity bears a specific proof mark signifying it has passed an official test or inspection.
-
E.
hasReportingMarkFormat
Indicates that one entity’s reporting mark follows or conforms to the specified format or pattern defined by the other 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_69f34971b75881908be360bb041f003c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e4a98550819097fd043a47d5bf99 |
completed | May 3, 2026, 6:01 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:37 a.m.