Triple
T20327249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OGLE-TR-182 |
E492370
|
entity |
| Predicate | hostStarOf |
P20818
|
FINISHED |
| Object | OGLE-TR-182b |
—
|
NE NERFINISHED |
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: OGLE-TR-182b | Statement: [OGLE-TR-182, hostStarOf, OGLE-TR-182b]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OGLE-TR-182b Context triple: [OGLE-TR-182, hostStarOf, OGLE-TR-182b]
-
A.
OGLE-TR-182b
chosen
OGLE-TR-182b is a transiting exoplanet, likely a hot Jupiter, discovered orbiting the distant star OGLE-TR-182 in the constellation Carina.
-
B.
OGLE-TR-182
OGLE-TR-182 is a distant star known for hosting a transiting exoplanet, discovered by the OGLE survey in the constellation Tucana.
-
C.
OGLE-TR-10b
OGLE-TR-10b is a hot Jupiter–type exoplanet discovered via the transit method, orbiting very close to the Sun-like star OGLE-TR-10 in the constellation Sagittarius.
-
D.
OGLE-TR-113b
OGLE-TR-113b is a hot Jupiter–type exoplanet closely orbiting the star OGLE-TR-113, discovered via the transit method in the OGLE survey.
-
E.
OGLE-TR-132b
OGLE-TR-132b is a hot Jupiter–type exoplanet orbiting very close to its parent star in the constellation Carina, discovered via the transit method.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677e513608190b70527cd9f4d5da3 |
completed | April 20, 2026, 7 p.m. |
Created at: April 16, 2026, 11:21 a.m.