Triple
T37318122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Qastal |
E926393
|
entity |
| Predicate | pre1948BuiltEnvironment |
P98815
|
FINISHED |
| Object | stone houses |
—
|
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: stone houses | Statement: [al-Qastal, pre1948BuiltEnvironment, stone houses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pre1948BuiltEnvironment Context triple: [al-Qastal, pre1948BuiltEnvironment, stone houses]
-
A.
placeBuilt
Indicates that a structure or facility was constructed at a specific location.
-
B.
pre1948Status
chosen
Indicates the status or condition of an entity as it existed prior to the year 1948.
-
C.
builtHeritage
Indicates a relationship where a structure or site is recognized as part of the historically or culturally significant built environment.
-
D.
predecessorBuildingDate
Indicates that one building’s construction date precedes that of another building in a temporal sequence.
-
E.
hasFormerBuilding
Indicates that an entity previously occupied or used a different building, which is identified as its former building.
- 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_69f76eb28af88190b093b32e3fd614ab |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:16 p.m.