Triple
T33744782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | prasat |
E864668
|
entity |
| Predicate | oftenArrangedAs |
P46737
|
FINISHED |
| Object | single tower |
—
|
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: single tower | Statement: [prasat, oftenArrangedAs, single tower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenArrangedAs Context triple: [prasat, oftenArrangedAs, single tower]
-
A.
commonlyArrangedFor
Indicates that one entity is typically organized, scheduled, or set up on behalf of another entity.
-
B.
frequentlyArrangedFor
Indicates that one entity regularly organizes, schedules, or sets up something on behalf of another entity.
-
C.
isFrequentlyArrangedFor
Indicates that something is commonly or regularly organized, scheduled, or set up for a particular entity or purpose.
-
D.
arranges
Indicates that one entity organizes, coordinates, or puts in order some event, objects, or circumstances involving another entity.
-
E.
arrangementType
chosen
Indicates the specific kind or category of arrangement that characterizes how the related entities are organized or structured in relation to each other.
- 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_69f3498b24b8819096a65009e521d0e1 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: May 1, 2026, 1:44 a.m.