Triple
T31420680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vera Crux |
E801519
|
entity |
| Predicate | isConnectedWithEvent |
P10008
|
FINISHED |
| Object | discovery of the True Cross |
—
|
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: discovery of the True Cross | Statement: [Vera Crux, isConnectedWithEvent, discovery of the True Cross]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isConnectedWithEvent Context triple: [Vera Crux, isConnectedWithEvent, discovery of the True Cross]
-
A.
connectedToEvent
chosen
Indicates that an entity has a direct association or linkage with a specific event.
-
B.
isLinkedToEvent
Indicates that an entity has an association or connection with a specific event.
-
C.
connectsState
Indicates a relationship where one entity serves as a link or conduit between different states, conditions, or statuses of another entity.
-
D.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
E.
associatedWithEventHost
Indicates that an entity has a relationship or connection with the host of a particular event.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 30, 2026, 8:47 p.m.