Triple
T30464801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soldiers of the cross |
E775104
|
entity |
| Predicate | impliesIdentityAs |
P6594
|
FINISHED |
| Object | followers of Christ |
—
|
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: followers of Christ | Statement: [Soldiers of the cross, impliesIdentityAs, followers of Christ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impliesIdentityAs Context triple: [Soldiers of the cross, impliesIdentityAs, followers of Christ]
-
A.
impliesAttribute
Indicates that the presence or occurrence of one property, condition, or relation logically entails the existence or truth of another attribute.
-
B.
hasIdentity
chosen
Indicates that one entity is the same as, or is identified as, another specific entity or identifier.
-
C.
concludesIdentityIf
Indicates that one entity can infer or establish the identity of another entity as true or equivalent when certain conditions are met.
-
D.
impliesRankingAs
Indicates that one entity suggests, infers, or leads to the assignment of a particular ranking or ordered status to another entity.
-
E.
discoversIdentityAs
Indicates that an entity comes to realize or uncover its own true identity, nature, or role.
- 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f686f314fc81908a65eec389e8b1fb |
completed | May 2, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:11 p.m.