Triple
T30500149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | In Hoc Signo |
E776114
|
entity |
| Predicate | connectedToPerson |
P37306
|
FINISHED |
| Object | Constantine the Great |
—
|
NE NERFINISHED |
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: Constantine the Great | Statement: [In Hoc Signo, connectedToPerson, Constantine the Great]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedToPerson Context triple: [In Hoc Signo, connectedToPerson, Constantine the Great]
-
A.
connectedToPlace
Indicates that one entity has a spatial, functional, or relational link or association with a specific place.
-
B.
connectionTo
chosen
Indicates a relationship in which one entity is linked, associated, or otherwise related to another entity.
-
C.
formerlyConnectedTo
Indicates that two entities were once connected or associated in some way, but that connection no longer exists.
-
D.
notConnectedBy
Indicates that there is no direct link, path, or relationship connecting the referenced entities.
-
E.
connectedToOrganization
Indicates that an entity has a relationship or association with a particular organization, such as membership, affiliation, or formal linkage.
- 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: April 29, 2026, 8:14 p.m.