Triple
T19491557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Vergilius of Salzburg |
E487662
|
entity |
| Predicate | knownForView |
P102320
|
FINISHED |
| Object | Earth is spherical |
—
|
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: Earth is spherical | Statement: [Saint Vergilius of Salzburg, knownForView, Earth is spherical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownForView Context triple: [Saint Vergilius of Salzburg, knownForView, Earth is spherical]
-
A.
knownForPerspective
chosen
Indicates that an entity is recognized or notable for a particular viewpoint, angle, or way of seeing or interpreting something.
-
B.
knownForPosition
Indicates that an entity is notably recognized or distinguished for holding a particular position, role, or office.
-
C.
knownIn
Indicates that an entity is recognized, acknowledged, or familiar within a particular context, domain, or group.
-
D.
namedForKnownFor
Indicates that one entity is named after another entity specifically because that other entity is notable or recognized for something.
-
E.
knownForCollectionOf
Indicates that one entity is recognized or notable specifically for its collection or assemblage of another type of 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_69d8e8d9d1c88190b01cd78b8be49384 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6348e01b88190a513d0e256161fcd |
completed | April 20, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7883308190b73912a71a35a835 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.