Triple
T16287548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porter |
E395427
|
entity |
| Predicate | originalDuties |
P76671
|
FINISHED |
| Object | guarding entrances |
—
|
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: guarding entrances | Statement: [Porter, originalDuties, guarding entrances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalDuties Context triple: [Porter, originalDuties, guarding entrances]
-
A.
goalOfDuties
Indicates that something is the intended objective or purpose that a set of duties or responsibilities is meant to achieve.
-
B.
traditionalDuty
chosen
Indicates that an entity has an obligation or responsibility toward another entity or activity based on established customs, norms, or longstanding traditions.
-
C.
hasDutiesUnder
Indicates that one party is obligated to perform specific responsibilities or fulfill obligations as defined by another party, agreement, or authority.
-
D.
hasPrimaryDuty
Indicates that one entity holds the main or most important responsibility or obligation toward another entity or within a specified context.
-
E.
royalDuties
Indicates that an entity has responsibilities, obligations, or functions associated with a royal role or position.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24915a5948190a11b8e83b7974dda |
completed | April 17, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:05 a.m.