Triple
T25006372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wall |
E625849
|
entity |
| Predicate | ruleRegardingWall |
P157537
|
FINISHED |
| Object | no one may cross the wall without permission |
—
|
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: no one may cross the wall without permission | Statement: [Wall, ruleRegardingWall, no one may cross the wall without permission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruleRegardingWall Context triple: [Wall, ruleRegardingWall, no one may cross the wall without permission]
-
A.
hasWall
Indicates that one entity possesses, includes, or is bounded by a wall.
-
B.
hasWallRequirement
Indicates that an entity must satisfy a specified condition or standard related to walls (e.g., presence, type, or characteristics of walls).
-
C.
rulesAlongside
Indicates that two or more entities share governing authority or exercise power together over the same domain or group.
-
D.
positionInWall
Indicates that one entity occupies a specific location or placement within a wall.
-
E.
hasWallType
Indicates the specific kind or classification of wall associated with an entity.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44b113f8c8190ae05102e9c2ae076 |
completed | May 1, 2026, 6:41 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
| PDg | Predicate description generation | batch_69f448fe11f08190bdd53ca7ba2d51e4 |
completed | May 1, 2026, 6:32 a.m. |
Created at: April 18, 2026, 6:05 a.m.