Triple
T11461145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosemary Beach, Florida |
E271660
|
entity |
| Predicate | hasCovenants |
P99687
|
FINISHED |
| Object | architectural guidelines |
—
|
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: architectural guidelines | Statement: [Rosemary Beach, Florida, hasCovenants, architectural guidelines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCovenants Context triple: [Rosemary Beach, Florida, hasCovenants, architectural guidelines]
-
A.
covenantWith
Indicates a formal, binding agreement or promise established between two or more parties.
-
B.
covenantStatus
Indicates the current state or condition of a covenant or binding agreement between parties.
-
C.
covenantAssociation
Indicates a formal, binding relationship or agreement that associates entities under shared obligations, promises, or terms.
-
D.
relatedCovenant
Indicates a relationship in which one covenant is connected to, associated with, or derived from another covenant.
-
E.
covenantAdopted
Indicates that a covenant has been formally accepted and put into effect by the relevant party or parties.
- 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_69d6aadff8888190a13f253f0d460874 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d822f384f08190b1150ed1389dd31a |
completed | April 9, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69d80867ff248190bb157fa9e355353b |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d822ef46988190a1c360da4ee14fef |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:35 p.m.