Triple
T35529595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ark of Noah |
E1026762
|
entity |
| Predicate | builtAccordingTo |
P160600
|
FINISHED |
| Object | divine instructions |
—
|
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: divine instructions | Statement: [Ark of Noah, builtAccordingTo, divine instructions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtAccordingTo Context triple: [Ark of Noah, builtAccordingTo, divine instructions]
-
A.
builtType
Indicates the structural or construction type characterizing how something is built or formed.
-
B.
builtOn
Indicates that one entity is constructed, developed, or established using another entity as its base, foundation, or underlying platform.
-
C.
builtInThe
Indicates that something was constructed or created within a specified location, structure, or context.
-
D.
builtThrough
chosen
Indicates that something was created, developed, or achieved by means of a specified method, process, or intermediary.
-
E.
oftenBuiltBy
Indicates that something is frequently or commonly constructed or created by a particular agent or type of agent.
- 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:04 p.m.