Triple
T4891386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frentani |
E109569
|
entity |
| Predicate | eventualStatusInRome |
P13710
|
FINISHED |
| Object | Roman citizens |
—
|
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: Roman citizens | Statement: [Frentani, eventualStatusInRome, Roman citizens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventualStatusInRome Context triple: [Frentani, eventualStatusInRome, Roman citizens]
-
A.
administrativeStatusUnderRome
Indicates the type or level of administrative control or governance an entity was subject to within the Roman political system.
-
B.
laterStatus
chosen
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
-
C.
cityStatusUntil
Indicates the period up to a specified time during which a place holds or held a particular city status.
-
D.
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.
-
E.
preRomanStatus
Indicates the status or condition of an entity during the period before Roman rule or Roman cultural dominance.
- 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_69bd440f71348190b99938e59fb7f9a1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ffabccc81909115ece1b04e2061 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2e7b5c8190b8bf9d616dfa24f0 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:28 p.m.