Triple
T184355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Singel |
E3947
|
entity |
| Predicate | functionChange |
P6654
|
FINISHED |
| Object | from defensive moat to inner canal of canal belt |
—
|
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: from defensive moat to inner canal of canal belt | Statement: [Singel, functionChange, from defensive moat to inner canal of canal belt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionChange Context triple: [Singel, functionChange, from defensive moat to inner canal of canal belt]
-
A.
governanceChange
Indicates a change in the structure, rules, or authority of how an entity, organization, or system is governed.
-
B.
assignedFunction
Indicates that a specific role, duty, or function has been formally allocated to an entity.
-
C.
originalFunction
Indicates that one entity serves as the initial or primary function from which another function or behavior is derived or defined.
-
D.
committeeFunction
Indicates that a committee performs, is responsible for, or is associated with a particular function or role.
-
E.
formationEvent
Indicates the event or process through which something comes into existence, is created, or is initially established.
- 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a25926be9c8190a4cfce66f57589d1 |
completed | Feb. 28, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69a2566fb08c81908faff2fde552105d |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a257e763d081908c54ad57d8d3060d |
completed | Feb. 28, 2026, 2:50 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.