Triple
T12883126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porto Metro |
E308152
|
entity |
| Predicate | hasAtGradeSections |
P52096
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Porto Metro, hasAtGradeSections, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAtGradeSections Context triple: [Porto Metro, hasAtGradeSections, yes]
-
A.
atGradeSections
chosen
Indicates that certain sections or segments are located at ground level or share the same grade elevation relative to their surroundings.
-
B.
hasAtGradeStructure
Indicates that one entity includes or is associated with a structure located at ground level (at grade).
-
C.
hasGradesOrClasses
Indicates that an entity is associated with academic evaluations or enrolled instructional sessions, such as grades received or classes taken.
-
D.
hasGradeSystem
Indicates that one entity uses, follows, or is governed by a particular grading or evaluation system defined by another entity.
-
E.
hasGrades
Indicates that an entity possesses or is associated with one or more grade values, typically reflecting evaluations or scores.
- 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_69d7bdf69bc48190af6c2621f28ca351 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97c7f91d08190aac2f6419d3ba992 |
completed | April 10, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69d96fa55b888190ab1612e93c41aec4 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:39 p.m.