Triple
T9569654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Court of Arches |
E230881
|
entity |
| Predicate | appliesField |
P89856
|
FINISHED |
| Object | ecclesiastical law |
—
|
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: ecclesiastical law | Statement: [Court of Arches, appliesField, ecclesiastical law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesField Context triple: [Court of Arches, appliesField, ecclesiastical law]
-
A.
supportsField
Indicates that one entity provides the necessary structure, stability, or backing for a particular field, area, or domain associated with another entity.
-
B.
definesField
Indicates that one entity specifies or declares a particular field or attribute that belongs to or characterizes another entity.
-
C.
appliedAs
Indicates that one entity submitted itself or was put forward for consideration in a particular role, position, or context relative to another entity.
-
D.
fromField
Indicates that something originates in, is sourced from, or is associated with a particular field or domain.
-
E.
appliesFrom
Indicates that a rule, condition, or effect begins to be applicable starting from a specific point in time or state.
- F. None of above. chosen
Provenance (4 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_69ca847f22188190a56e4a97625bef22 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd998940c881909f9025512cf72fe9 |
completed | April 1, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69ccd59b960c8190966a8870a2426bd5 |
completed | April 1, 2026, 8:21 a.m. |
| PDg | Predicate description generation | batch_69ccd93e90048190a2b0d7c5c195ba98 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:04 p.m.