Triple
T32844217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hungarian customary law |
E840050
|
entity |
| Predicate | alsoAppliedIn |
P70805
|
FINISHED |
| Object | Transylvania |
—
|
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: Transylvania | Statement: [Hungarian customary law, alsoAppliedIn, Transylvania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoAppliedIn Context triple: [Hungarian customary law, alsoAppliedIn, Transylvania]
-
A.
appliesAlsoTo
chosen
Indicates that a condition, rule, or characteristic that applies to one entity is additionally applicable to another entity.
-
B.
alsoUsedIn
Indicates that something is additionally employed, applied, or present in another context, setting, or use case beyond the primary one.
-
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.
appliesVia
Indicates that an action, rule, or effect is carried out, implemented, or achieved through a specified method, medium, or mechanism.
-
E.
appliedFrom
Indicates that an application or request was initiated starting at or originating from a particular source, location, or context.
- 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_69f3493ff0888190b51e974eae2a7834 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:16 a.m.