Triple
T2563930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article XXXVII Of the Civil Magistrates |
E57305
|
entity |
| Predicate | concernsRelationBetween |
P34778
|
FINISHED |
| Object | church |
—
|
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: church | Statement: [Article XXXVII Of the Civil Magistrates, concernsRelationBetween, church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concernsRelationBetween Context triple: [Article XXXVII Of the Civil Magistrates, concernsRelationBetween, church]
-
A.
valueRelation
Indicates a comparative or associative relationship between the values or magnitudes of two or more entities.
-
B.
titleRelation
Indicates a relationship where one entity serves as the title, designation, or formal name associated with another entity.
-
C.
concernsRight
Indicates that something is about or relates specifically to a legal or moral right held by an entity.
-
D.
termRelationTo
chosen
Indicates a general relational association between one term and another, without specifying the exact nature of that relationship.
-
E.
concern
Indicates that one entity is about, relates to, or is of interest or importance to another entity.
- 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_69ab4a4ef9008190a0e6d4422b9418b7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd35c6ee88190b6eaa1841d3e99a4 |
completed | March 7, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69abd0cc8d308190ae7aa32b8f5ae2e5 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.