Triple

T38519469
Position Surface form Disambiguated ID Type / Status
Subject Laodicea E922432 entity
Predicate rebuiltWith P190977 FINISHED
Object its own resources after 60 AD earthquake 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: its own resources after 60 AD earthquake | Statement: [Laodicea, rebuiltWith, its own resources after 60 AD earthquake]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: rebuiltWith
Context triple: [Laodicea, rebuiltWith, its own resources after 60 AD earthquake]
  • A. rebuiltFor
    Indicates that one entity has been reconstructed, renovated, or modified specifically to serve the needs, purposes, or use of another entity.
  • B. rebuiltUnder
    Indicates that an entity was reconstructed or restored while being subject to the authority, control, or governance of another entity.
  • C. rebuiltOn
    Indicates that one entity has been reconstructed, restored, or built again on, over, or using the foundation, structure, or basis of another entity.
  • D. rebuiltEvery
    Indicates that one entity is reconstructed or built anew at regular intervals defined by another entity.
  • E. rebuild
    Indicates restoring or constructing again something that was previously built, often after damage, destruction, or significant alteration.
  • 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_69f76ea5f5588190bd0b28c82e975640 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fcd34596288190b8e34a7a20b4c0db completed May 7, 2026, 6 p.m.
PD Predicate disambiguation batch_69fcd1f6b2e08190bf0300ae7c9ae67a completed May 7, 2026, 5:55 p.m.
PDg Predicate description generation batch_69fcd31227708190a7df213597e66ca8 completed May 7, 2026, 5:59 p.m.
Created at: May 3, 2026, 4:32 p.m.