Triple
T13327429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galatians |
E317475
|
entity |
| Predicate | romanClientStatus |
P63218
|
FINISHED |
| Object | 2nd century BC |
—
|
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: 2nd century BC | Statement: [Galatians, romanClientStatus, 2nd century BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanClientStatus Context triple: [Galatians, romanClientStatus, 2nd century BC]
-
A.
romanStatus
chosen
Indicates the status or condition of an entity within a Roman-specific context, such as its legal, social, or civic standing in Roman society.
-
B.
registrationStatus
Indicates the current state or condition of an entity’s enrollment or registration within a given system or process.
-
C.
classStatus
Indicates the current academic or enrollment standing of an entity within a class or course context.
-
D.
customStatus
Indicates that an entity has a user-defined or non-standard status assigned to it.
-
E.
cultStatusInRome
Indicates that an entity holds or is associated with a recognized cultic or religious status within the context of Rome.
- 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_69d806b4d62c81908d4ced1665414be5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6babd88190a5d529df9584b9a4 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:30 p.m.