Triple
T21444558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The House-top |
E529034
|
entity |
| Predicate | hasLineation |
P144367
|
FINISHED |
| Object | irregular meter |
—
|
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: irregular meter | Statement: [The House-top, hasLineation, irregular meter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLineation Context triple: [The House-top, hasLineation, irregular meter]
-
A.
hasLineStructure
Indicates that one entity possesses or exhibits a linear arrangement or organization of its components.
-
B.
isLinedWith
Indicates that one object or surface is covered, edged, or internally coated along its length or area with another material or layer.
-
C.
hasDominantLines
Indicates that one element in a pair exhibits stronger, more prominent, or controlling linear features relative to the other.
-
D.
hasDeFactoLine
Indicates that there exists an unofficial or non-legally recognized boundary or demarcation line functioning in practice between the related entities.
-
E.
hasLineSection
Indicates that an entity includes, contains, or is composed of a specific segment or section of a line.
- 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_69e0c457579481909db68053ed99750c |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b70630ac8190b031e31ffa2c358e |
completed | April 22, 2026, 11:54 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e63d2aca38819094d312078feaa436 |
completed | April 20, 2026, 2:50 p.m. |
Created at: April 16, 2026, 6:05 p.m.