Triple
T36839502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Eustachio, Rome |
E910364
|
entity |
| Predicate | hasTraditionalNumber |
P201584
|
FINISHED |
| Object | rione VIII |
—
|
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: rione VIII | Statement: [San Eustachio, Rome, hasTraditionalNumber, rione VIII]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalNumber Context triple: [San Eustachio, Rome, hasTraditionalNumber, rione VIII]
-
A.
hasTraditionalSymbol
Indicates that something is associated with or represented by a conventional or culturally established symbol.
-
B.
hasTraditionalValue
Indicates that something embodies, reflects, or is associated with long-established customs, norms, or cultural values.
-
C.
hasTraditionalName
Indicates that an entity is associated with a name traditionally used or recognized for it, often rooted in long-standing cultural or historical practice.
-
D.
hasTraditionalDay
Indicates that an entity is associated with a specific traditional or customary day dedicated to it.
-
E.
isTraditional
Indicates that something adheres to long-established customs, practices, or norms rather than modern or innovative ones.
- F. None of above. chosen
Provenance (4 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_69f76e7f65a881908651b702da592b6d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a0008225cc081909ff1fd0639859dc4 |
completed | May 10, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_6a0007bac5d8819098aff8031d4abe5d |
completed | May 10, 2026, 4:21 a.m. |
| PDg | Predicate description generation | batch_6a000821b12c819093ca3b3dc0cff370 |
completed | May 10, 2026, 4:22 a.m. |
Created at: May 3, 2026, 4:13 p.m.