Triple
T9966672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amphibian Man |
E195699
|
entity |
| Predicate | formsBondType |
P49770
|
FINISHED |
| Object | romantic relationship |
—
|
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: romantic relationship | Statement: [Amphibian Man, formsBondType, romantic relationship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsBondType Context triple: [Amphibian Man, formsBondType, romantic relationship]
-
A.
bondedWith
Indicates that two entities are joined by a strong, enduring connection or attachment, whether emotional, social, or structural.
-
B.
hasBondType
chosen
Indicates the specific kind of bond or connection that exists between two related entities.
-
C.
formationType
Indicates the specific structural or organizational configuration in which something is arranged, created, or formed.
-
D.
pairBond
Indicates a long-term, typically exclusive social or reproductive partnership formed between two individuals.
-
E.
formsWith
Indicates that one entity combines or associates with another to create or constitute a joint structure, group, or configuration.
- 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_69ca82ebd1288190912f9e4482d1fa35 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb71dc50081909329722dc087c9f6 |
completed | April 2, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9ae19c819099fb3635e57c79be |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:47 p.m.