Triple
T38105566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Natural Monument (Japan) |
E951499
|
entity |
| Predicate | managementPlanRequired |
P142794
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Natural Monument (Japan), managementPlanRequired, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managementPlanRequired Context triple: [Natural Monument (Japan), managementPlanRequired, yes]
-
A.
managementPlanSpecifies
Indicates that a management plan explicitly defines or details specific actions, procedures, or conditions to be followed.
-
B.
hasManagementPlan
Indicates that an entity is associated with a defined management plan specifying how it should be overseen, maintained, or administered.
-
C.
managementNeed
Indicates that one entity requires oversight, direction, or administrative control from another entity.
-
D.
planningRequirement
chosen
Indicates that one entity imposes or specifies a planning-related obligation, condition, or prerequisite that must be satisfied by another entity or activity.
-
E.
maintenanceRequirement
Indicates that an entity is obligated to perform, schedule, or adhere to specific maintenance activities or conditions for another entity or system.
- 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_69f76f065ed08190bdfb1b6d817f5b39 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: May 3, 2026, 4:21 p.m.