Triple
T29766947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paraiso |
E753938
|
entity |
| Predicate | functionDuringCanalZone |
P122857
|
FINISHED |
| Object | residential area for canal employees |
—
|
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: residential area for canal employees | Statement: [Paraiso, functionDuringCanalZone, residential area for canal employees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionDuringCanalZone Context triple: [Paraiso, functionDuringCanalZone, residential area for canal employees]
-
A.
positionInCanal
Indicates that an entity occupies a specific location within a canal.
-
B.
functionDuringBattle
Indicates a functional role, effect, or behavior that specifically occurs or is active during a battle.
-
C.
containsCanal
Indicates that one geographical or spatial entity has a canal located within its boundaries or interior.
-
D.
allowsCanalTraffic
Indicates that something permits or enables the passage of vessels or waterborne transport through a canal.
-
E.
functionDuringPeriod
chosen
Indicates that a function, role, or activity is performed or valid throughout a specified time period.
- 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_69f0ef827ff88190ade56e0b0846b713 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 28, 2026, 8:38 p.m.